Paket.Core
12.0.0-alpha004
See the version list below for details.
dotnet add package Paket.Core --version 12.0.0-alpha004
NuGet\Install-Package Paket.Core -Version 12.0.0-alpha004
<PackageReference Include="Paket.Core" Version="12.0.0-alpha004" />
<PackageVersion Include="Paket.Core" Version="12.0.0-alpha004" />
<PackageReference Include="Paket.Core" />
paket add Paket.Core --version 12.0.0-alpha004
#r "nuget: Paket.Core, 12.0.0-alpha004"
#:package Paket.Core@12.0.0-alpha004
#addin nuget:?package=Paket.Core&version=12.0.0-alpha004&prerelease
#tool nuget:?package=Paket.Core&version=12.0.0-alpha004&prerelease
Paket
A dependency manager for .NET with support for NuGet packages and git repositories.
Why Paket?
NuGet did not separate out the concept of transitive dependencies. If you install a package into your project and that package has further dependencies then all transitive packages are included in the packages.config. There is no way to tell which packages are only transitive dependencies.
Even more importantly: If two packages reference conflicting versions of a package, NuGet will silently take the latest version (read more). You have no control over this process.
Paket on the other hand maintains this information on a consistent and stable basis within the paket.lock file in the solution root.
This file, together with the paket.dependencies file enables you to determine exactly what's happening with your dependencies.
Paket also enables you to reference files directly from git repositories or any http-resource.
For more reasons see the FAQ.
Online resources
- Source code
- Documentation
- Getting started guide
- Install the Paket .NET tool:
dotnet tool install paket
Troubleshooting and support
- Found a bug or missing a feature? Feed the issue tracker.
- Announcements and related miscellanea through Twitter (@PaketManager)
Quick contributing guide
- Fork and clone locally.
- Build the solution with Visual Studio,
build.cmdorbuild.sh. - Create a topic specific branch in git. Add a nice feature in the code. Do not forget to add tests and/or docs.
- Run
build.cmd(build.shon Linux/macOS) to make sure all tests are still passing. - When built, you'll find the binaries in
./binwhich you can then test with locally, to ensure the bug or feature has been successfully implemented. - Send a Pull Request.
If you want to contribute to the docs then please modify the markdown files in /docs/content and send a pull request.
Note, that short description and syntax for each command is generated automatically from the Paket.Commands module.
License
The MIT license
Maintainer(s)
The default maintainer account for projects under "fsprojects" is @fsprojectsgit - F# Community Project Incubation Space (repo management)
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Chessie (>= 0.6.0)
- Fake.IO.FileSystem (>= 6.2.0 && < 7.0.0)
- FSharp.Core (>= 9.0.303)
- Mono.Cecil (>= 0.11.6 && < 0.12.0)
- Newtonsoft.Json (>= 13.0.4)
- Nuget.Packaging (>= 7.9.0)
- System.Net.Http.WinHttpHandler (>= 10.0.14)
- System.Security.Cryptography.ProtectedData (>= 10.0.14)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on Paket.Core:
| Package | Downloads |
|---|---|
|
Fake.Runtime
FAKE - F# Make - is a build automation tool for .NET. Tasks and dependencies are specified in a DSL which is integrated in F#. |
|
|
dotnet-fake
FAKE - F# Make - is a build automation tool for .NET. Tasks and dependencies are specified in a DSL which is integrated in F#. |
|
|
Tfs.Build.Paket
A set of TFS build tasks around getting and using paket |
|
|
Queil.FSharp.DependencyManager.Paket
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 12.0.0-alpha006 | 0 | 11/8/2026 |
| 12.0.0-alpha005 | 44 | 11/7/2026 |
| 12.0.0-alpha004 | 236 | 11/1/2026 |
| 12.0.0-alpha003 | 123 | 10/26/2026 |
| 12.0.0-alpha002 | 174 | 10/17/2026 |
| 12.0.0-alpha001 | 219 | 10/11/2026 |
| 11.0.1 | 1,465 | 10/11/2026 |
| 11.0.0 | 1,089 | 10/5/2026 |
| 11.0.0-alpha004 | 106 | 10/5/2026 |
| 11.0.0-alpha003 | 116 | 9/27/2026 |
| 10.3.1 | 6,151 | 1/20/2026 |
| 10.2.1 | 2,543 | 1/19/2026 |
| 10.2.0 | 173 | 1/19/2026 |
| 10.1.1 | 207 | 1/19/2026 |
| 10.0.1 | 209 | 1/19/2026 |
| 10.0.0-alpha011 | 8,591 | 11/11/2025 |
| 10.0.0-alpha009 | 387 | 11/11/2025 |
| 10.0.0-alpha007 | 358 | 11/11/2025 |
| 10.0.0-alpha006 | 352 | 11/11/2025 |
| 10.0.0-alpha005 | 356 | 11/11/2025 |
BREAKING: `paket pack --release-notes-file` reads the file with Fake.Core.ReleaseNotes 6, in the formats described in https://fake.build/reference/fake-core-releasenotes.html: the package version is the first word of the latest header that is a whole SemVer version, so `## [1.2.3] - 2020-01-01` and `## v1.2.3 - 2020-01-01` give `2020-01-01`; pass `--version` for such headers. Prerelease versions like `1.2.3-beta.11.2` are no longer cut, and build metadata (`+sha.abc`) is kept - https://github.com/fsprojects/FAKE/pull/2686
Looking for projects no longer runs forever on a cyclic directory link, as in a Nix `.devenv` profile. `paket pack` still follows the links when it looks for template files - https://github.com/fsprojects/Paket/pull/4421 @michaelglass
BREAKING: Paket no longer looks for projects and `paket.template` files in the folders whose name starts with a dot, like `.devenv`, nor in the folders that are links, as `paket convert-from-nuget` already did for the solutions and NuGet files: the projects there are left out of install, restore, update, remove and pack. Until now only `.git` and `.fable` were skipped. A cyclic link, as in a Nix `.devenv` profile, no longer makes the search run forever - https://github.com/fsprojects/Paket/pull/4421
BREAKING: The obsolete `InstallModel.CreateFromLibs` and `InstallModel.createFromLibs`, `InstallModel.GetLibReferences` and `PlatformMatching.getFrameworkPathPenalty` of Paket.Core are removed: use `InstallModel.CreateFromContent` and `createFromContent`, `GetLegacyReferences` or `GetCompileReferences`, and `PlatformMatching.getPathPenalty`. So is the `Fake.Globbing` module that Paket.Core carried from FAKE 4: use `Fake.IO.Globbing.Glob` of the Fake.IO.FileSystem package. So are `NuGetCache.NuGetConfig.writeNuGetConfig` and `Constants.NuGetConfigFile`, unused since the end of the project.json support
The warning about the FSharp.Core binding redirects of F# projects links to an existing section of the documentation
Update Argu from 6.1.1 to 6.2.5, and System.Configuration.ConfigurationManager from 4.7 to 10.0, so the `paket` tool no longer ships System.Drawing.Common 4.7 and its critical vulnerability (GHSA-rxg9-xrhp-64gj). The help of `paket update`, `paket find-packages` and `paket generate-nuspec` no longer shows their optional package ID, search text and `output` directory as required