NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2642 most downloaded on NuGet
A .NET Core global tool to generate CycloneDX bill-of-material documents for use with Software Composition Analysis (SCA).
Latest stable
6.3.1
Last release 1 months ago
12 Oct 2026
Release timing varies
gaps range from 8 days to 6 months
Some releases are documented
notes for 30 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
80 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Fixes a regression in 6.3.0 where Microsoft.ML.OnnxRuntime.Gpu and its managed/native dependencies were classified as development-only and removed by
Fixes a regression in 6.3.0 where Microsoft.ML.OnnxRuntime.Gpu and its managed/native dependencies were classified as development-only and removed by --exclude-dev (#1139, #1140).
Build-only runtime aggregation wrappers are now retained as Required when their restored dependency closure provides positive evidence in an allowed runtime-capable category. The refinement is target-local and preserves explicit development-only asset selections, standalone build-only/analyzer/tool filtering, test-only exclusion, and production runtime sharing.
Restored dependency graphs cannot distinguish every runtime wrapper from a build-tool wrapper with the same observable assets. Conservative retention may therefore also retain ambiguous build-tool closures. PrivateAssets controls propagation, not development intent, and alone does not guarantee exclusion. This is not an exact publish-output scanner.
Cross-platform .NET CI and Docker E2E tests pass. A real consumer referencing only Microsoft.ML.OnnxRuntime.Gpu 1.25.1 was also restored and published for linux-x64; native runtime loading and XML/JSON SBOM closure retention with --exclude-dev were verified. GPU inference was not tested.
Thank you @wahyuen (Wah Yuen) for reporting the regression and providing the reproduction details!
dotnet tool update --global CycloneDX --version 6.3.1Docker image: cyclonedx/cyclonedx-dotnet:6.3.1 (also published as latest).
Your coding agent can read these notes before it upgrades. Set up the MCP server →
--exclude-dev. Explicit development-only asset selections,
standalone build-only packages without such evidence, and analyzer/tool-only roots remain
development roots; separate production runtime sharing still wins, and test-project-only
use is still filtered. PrivateAssets controls propagation, not development intent.
Ambiguous build-tool closures may also be retained; this is not
publish-output analysis. Thanks to @wahyuen for reporting the regression.--exclude-dev is deprecated but continues to filter : it omits development-only and test-project-only packages while retaining packages shared with pr…
--set-nuget-purl with --include-project-references generates missing project purls. Existing purls and custom BOM references are preserved, and dependency edges use the final references.scope="excluded". Packages shared with production runtime use remain required.--exclude-dev is deprecated but continues to filter: it omits development-only and test-project-only packages while retaining packages shared with production runtime use.$(RootNamespace) in assembly names, including nested $(MSBuildProjectName) tokens. Missing, empty, or circular $(AssemblyName)-referencing namespaces fall back to the project filename. This is best-effort substitution, not full MSBuild evaluation.--exclude-filter removes only packages it newly orphans; pre-existing orphans are retained.net48, netstandard2.0, Net8.0, and Windows-qualified TFMs. The underlying NuGet.ProjectModel 7.6.0 fix was already included in 6.2.1.Thanks to everyone who contributed code, tests, and issue reports to this release:
A warm welcome and a big thank you to our first-time contributors:
Full changelog: v6.2.1...v6.3.0
--set-nuget-purl
is combined with --include-project-references, only missing project purls are generated.
Missing or default <name>@<version> bom-refs use the available purl; existing purls and
custom bom-refs are preserved. Dependency edges use the final references. Root metadata
and NuGet package identifier behavior is unchanged.scope="excluded";
runtime-shared packages remain required. The deprecated --exclude-dev option continues to
filter, omitting development-only and test-project-only packages (including ordinary runtime
dependencies of test projects), while retaining packages shared with production runtime use.Resolve $(RootNamespace) in project assembly names (#1128, fixes #917) — substitute the
project's explicit root namespace, including $(MSBuildProjectName) within it, so referenced
projects using this pattern no longer collide under an unresolved name. Missing, empty, or
$(AssemblyName)-referencing root namespaces fall back to the project filename. This is
best-effort substitution, not general MSBuild property evaluation.
--exclude-filter removes only what it orphans (#1135, fixes #1133) — pre-existing orphans
are kept.
Regression coverage for --exclude-filter on non-normalized target frameworks (#1131,
fixes #1126) — verifies that direct references remain detected for net48, netstandard2.0,
Net8.0 and net8.0-windows10.0.19041.0, rather than removing every package as an orphan.
The underlying fix comes from NuGet.ProjectModel 7.6.0, already included in 6.2.1.
This patch release fixes dependency resolution in multi-project solutions and hash computation for uncached NuGet packages.
This patch release fixes dependency resolution in multi-project solutions and hash computation for uncached NuGet packages.
Sequence contains more than one matching element when multiple merged package versions satisfy an unresolved NuGet dependency range. The BOM now retains a dependency edge to every matching component..nupkg.Thanks to everyone who contributed to this release:
Full changelog: v6.2.0...v6.2.1
Suppress aka.ms/deprecateLicenseUrl stub URL ( #1011 ) — NuGet auto-injects https://aka.ms/deprecateLicenseUrl\ into for packages packed with ; this U…
Thanks to everyone who contributed to this release:
--configuration / -c CLI option (#1056, fixes #1028) — passes -p:Configuration=<value> to dotnet restore so MSBuild evaluates conditional PackageReference items during restore. Configuration-specific packages (e.g. debug-only Avalonia.Diagnostics) are no longer included in the SBOM when a Release configuration is requested.<license type="file"> now have their license file embedded as base64-encoded text in the BOM when --include-license-text is specified; without the flag the license is still detected but not embeddedaka.ms/deprecateLicenseUrl stub URL (#1011) — NuGet auto-injects https://aka.ms/deprecateLicenseUrl into <licenseUrl> for packages packed with <license type="file">; this URL is now correctly ignored rather than being emitted as a license entry in the BOM (see NuGet spec)<licenseUrl> no longer produce a spurious License { Name="Unknown - See URL", Url=null } node in the BOMUNLICENSED emitted as SPDX id (#1004, fixes #915) — UNLICENSED is a NuGet-specific token that is not a valid SPDX identifier; it is now emitted as license.name instead of license.id to keep BOM output validconfiguration parameter with method overloads — addresses Codacy "Use the overloading mechanism instead of the optional parameters" findings on IDotnetUtilsService.Restore, IProjectFileService.GetProjectDotnetDependencysAsync / RecursivelyGetProjectDotnetDependencysAsync, and ISolutionFileService.GetSolutionDotnetDependencysUtils.UseUnsafeRelaxedJsonEscaping global flagsetup-dotnet steps to avoid macOS timeoutdocs/license-resolution.md) — documents the four-phase license resolution pipeline used by the tool--configuration — new Verify-based BOM snapshot tests covering TestPkg.UrlLicense, TestPkg.SpdxLicense, TestPkg.FileLicense, and conditional PackageReference scenarios with and without the --configuration flagFix crash when a nuspec declares an exact-range version constraint across multiple projects ( #1071 ) — when a package's nuspec dependency uses an exa
[1.0.0]) and multiple versions of that package are present in a multi-project solution, the tool no longer crashes with "Unable to locate valid bom ref"; the dependency edge is resolved to the version that satisfies the rangeUse tools/components instead of deprecated tools/tool ( #1043 ) — BOM metadata now uses the non-deprecated CycloneDX structure for recording tool info…
bom/1.7 schema namespace--exclude filter no longer requires a version to be specifiedAssemblyName in projects using the default XML namespacetools/components instead of deprecated tools/tool (#1043) — BOM metadata now uses the non-deprecated CycloneDX structure for recording tool information⚠️ WARNING: This is a MAJOR release with breaking changes.
⚠️ WARNING: This is a MAJOR release with breaking changes.
This release includes multiple significant changes that may affect compatibility:
- Removed deprecated CLI arguments - Several CLI flags have been removed. Scripts, CI/CD pipelines, and automation using these flags will break.
- Upgraded to .NET 10 - Runtime requirements have changed.
- Updated System.CommandLine - Upgraded from beta4 to v2.0.0 final, which includes breaking API changes that may affect command-line behavior.
- Updated dependency versions - NuGet packages, System.IO.Abstractions, and other dependencies have been upgraded.
Action required: Test thoroughly in a non-production environment before upgrading. Review all sections below for changes that may affect your use case.
Remove deprecated CLI arguments (#996, 0ae5d6a)
-f flag (replaced by -fn/--filename)-d flag (replaced by -ed/--exclude-dev)-r flag (replaced by -rs/--scan-project-references)--disable-github-licenses/-dgl flag (already default behavior)--out and --json flag were not removed in this release for backward compatibility but are still deprecated and will be removed in a future release.Upgraded System.CommandLine to v2.0.0 (#989, e11f8e7)
2.0.0-beta4.22272.1 to 2.0.0 (stable release)Minimum .NET runtime requirement (#989, e11f8e7)
mcr.microsoft.com/dotnet/sdk:10.0Dockerfile improvements (#993, edf2bd9)
DOTNET_CLI_HOME, NUGET_PACKAGES/tmp/dotnet-home and /tmp/nuget-packages writable for any user (chmod 0755)CycloneDX to dotnet /app/CycloneDX.dllpath argument optional with ArgumentArity.ZeroOrOneUpgrade to .NET 10 (#989, e11f8e7)
net10.0mcr.microsoft.com/dotnet/sdk:10.0Dependency updates
Workflow security hardening (#975, 39b8986)
permissions: contents: read to permissions: read-allPin GitHub Actions versions (1145c82)
Enable NuGet package locking (#972, fad44df)
packages.lock.json files for both main and test projectsRestorePackagesWithLockFile in Directory.Build.propsUpdate NuGet dependencies (#973, e930da1)
NuGet.ProjectModel from 6.9.1 to 6.14.0NuGet.Protocol from 6.9.1 to 6.14.0⚠️ WARNING: This is a MAJOR release with breaking changes.
This release includes multiple significant changes that may affect compatibility:
- Removed deprecated CLI arguments - Several CLI flags have been removed. Scripts, CI/CD pipelines, and automation using these flags will break.
- Upgraded to .NET 10 - Runtime requirements have changed.
- Updated System.CommandLine - Upgraded from beta4 to v2.0.0 final, which includes breaking API changes that may affect command-line behavior.
- Updated dependency versions - NuGet packages, System.IO.Abstractions, and other dependencies have been upgraded.
Action required: Test thoroughly in a non-production environment before upgrading. Review all sections below for changes that may affect your use case.
Remove deprecated CLI arguments (#996, 0ae5d6a)
--json/-j flag (replaced by --output-format json)-f flag (replaced by -fn/--filename)-d flag (replaced by -ed/--exclude-dev)-r flag (replaced by -rs/--scan-project-references)--disable-github-licenses/-dgl flag (already default behavior)json property from RunOptions modeloutputFormat enum instead of boolean json flagProgram.cs and Runner.cs--out flag was restored before release for backward compatibility (see Fixed section below)Upgraded System.CommandLine to v2.0.0 (#989, e11f8e7)
2.0.0-beta4.22272.1 to 2.0.0 (stable release)Minimum .NET runtime requirement (#989, e11f8e7)
mcr.microsoft.com/dotnet/sdk:10.0.slnx format to supported file types in READMEDockerfile improvements (#993, edf2bd9)
DOTNET_CLI_HOME, NUGET_PACKAGES/tmp/dotnet-home and /tmp/nuget-packages writable for any user (chmod 0755)CycloneDX to dotnet /app/CycloneDX.dllpath argument optional with ArgumentArity.ZeroOrOneUpgrade to .NET 10 (#989, e11f8e7)
net10.0mcr.microsoft.com/dotnet/sdk:10.0Dependency updates
Restore --out parameter for backward compatibility
--out flag as a deprecated alias for --output/-o to maintain compatibility with existing GitHub Actions and CI/CD pipelines--output instead--output and --out are provided, --output takes precedenceRestore --json parameter for backward compatibility
--json flag as a deprecated alias for --output-format json to maintain compatibility with existing GitHub Actions and CI/CD pipelines--output-format instead--json is provided, it sets the output format to JSONMissing using statement (161766f)
using System; directive in Program.csWorkflow security hardening (#975, 39b8986)
permissions: contents: read to permissions: read-allPin GitHub Actions versions (1145c82)
Enable NuGet package locking (#972, fad44df)
packages.lock.json files for both main and test projectsRestorePackagesWithLockFile in Directory.Build.propsUpdate NuGet dependencies (#973, e930da1)
NuGet.ProjectModel from 6.9.1 to 6.14.0NuGet.Protocol from 6.9.1 to 6.14.0🚀 CycloneDX .NET v5.5.0 Release Notes
.csproj file locations in .slnf files — paths are now correctly resolved relative to the .sln file. [#967](#967) (thanks [@uo-uhbc](https://github.com/uo-uhbc))IsTestProject detection to use the correct XML namespace when parsing project files. [#938](#938) (thanks [@benavidezb](https://github.com/benavidezb))[v5.4.0 → v5.5.0](v5.4.0...v5.5.0)
Add support for solution filter file ( #853 ) by @michha in #920
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v5.3.2...v5.4.0
🚀 CycloneDX .NET v5.3.2 Release Notes
Addressed the performance regression introduced in v5.3.1 that caused longer execution times. The CLI now attempts to locate the project.assets.json at its default location before falling back to invoking dotnet msbuild, restoring execution speed for projects that use the default /obj directory. #960
⚠️ The previously used --json flag is now deprecated and will be removed in a future release. Use --format json instead for the same behavior—with mor…
We’re aware of a performance problems introduced in v5.3.1 that can significantly increase execution time, most likely when scanning large .sln files. SBOM generation may take noticeably longer compared to previous versions. We're investigating the root cause and working on improvements for a future release.
✅ This has been fixed in v5.3.2
Analyzer Support for MSBuild-based project.assets.json Resolution – The CLI now supports analysis of MSBuild-based projects by resolving project.assets.json using MSBuild context. This improves compatibility with SDK-style projects. #952.
New --output-format Parameter (Replaces --json) – A new --output-format parameter has been added, allowing explicit selection of output format (json, xml, unsafejson, or auto).
⚠️ The previously used --json flag is now deprecated and will be removed in a future release. Use --format json instead for the same behavior—with more flexibility.
(https://github.com/mtsfoni) in #953.
CycloneDX Format v1.6.1 – BOMs are now generated using the CycloneDX 1.6.1 specification, ensuring compatibility with the latest schema and supporting new fields/features defined in the spec.
📜 Full Changelog: v5.2.0 → v5.3.1
Nothing published for this version
Fix Error with Uppercase Characters in Version Strings by @JohnHunhoff in #902
Full Changelog: v5.1.1...v5.2.0
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v5.1.1...v5.2.0
Fixes a null reference exception that can occur in v5.1.0
Fixes a null reference exception that can occur in v5.1.0
Full Changelog: v5.1.0...v5.1.1
> This version is defect, use v5.1.1 instead
[!CAUTION] This version is defect, use v5.1.1 instead
.slnx Solutions – Added support for analyzing .slnx solutions. Thanks to @MMonrad in #933.A warm welcome to our first-time contributors:
📜 Full Changelog: v5.0.1 → v5.1.0
VCS URL Normalization – Resolved schema validation errors caused by Git-style URLs (e.g., git@github.com:user/repo.git) by converting them to valid UR
git@github.com:user/repo.git) by converting them to valid URL formats, enhancing compatibility with tools like Dependency-Track. Thanks to @Alex-Stevens in #910. Issue #890xunit from 2.7.0 to 2.9.3 by @dependabot in #924.xunit.runner.visualstudio from 2.5.7 to 3.0.1 by @dependabot in #925.A big thank you to our first-time contributor:
📜 Full Changelog: v5.0.0 → v5.0.1
cyclonedx-dotnet no longer runs on .NET 6 and .NET 7. However, you can still generate SBOMs for applications targeting these versions.
cyclonedx-dotnet no longer runs on .NET 6 and .NET 7. However, you can still generate SBOMs for applications targeting these versions.cyclonedx-dotnet now runs on .NET 9 by @nathan-mittelette in #914.A big thank you to our first-time contributors:
📜 Full Changelog: [v4.2.0 → v5.0.0](https://github.com/CycloneDX/cyclonedx-dotnet/compare/v4.2.0...v5.0.0)
Dockerimage is now based sdk:9.0
feat: Support X# Project files (#895) by @VolkmarR in https://github.com/CycloneDX/cyclonedx-dotnet/pull/900
RollForward to run on the latest .NET SDKs by @nil4 in https://github.com/CycloneDX/cyclonedx-dotnet/pull/909Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v4.0.0...v4.1.0
Potentially Breaking: Update CycloneDX to 8.0.0 and BOM validation to v1_6 by @MarioAllegro in https://github.com/CycloneDX/cyclonedx-dotnet/pull/907
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v3.0.8...v4.0.0
fix: Also find assembly version info for VB projects by @dhivarson in https://github.com/CycloneDX/cyclonedx-dotnet/pull/870
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v3.0.7...v3.0.8
chore: bump CycloneDX.Core to 7.0.1 by @mtsfoni in https://github.com/CycloneDX/cyclonedx-dotnet/pull/879
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v3.0.6...v3.0.7
Corrected an issue where an error occurred while reading a read-only .csproj file.
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v3.0.5...v3.0.6
Fixed a crash, when a referenced project file is missing. This issue can arise if the ProjectReference in the project file is conditional. (Issue #826
Bug Fixes:
-rs was used with asset-files and a child project had multiple targets with differing dependencies. (Issue #830)-rs setting, dependencies that relied on the root project were under some circumstances incorrectly positioned in the dependency graph.-rs and -ipr, project references were not accurately placed in the dependency graph.A floating version in project references caused a System.ArgumentException and broke the generation process.
A floating version in project references caused a System.ArgumentException and broke the generation process. (https://github.com/CycloneDX/cyclonedx-dotnet/issues/814)
Restores functionality, that a timestamp in the metadata is automatically generated if not provided in the metadata file.
Restores functionality, that a timestamp in the metadata is automatically generated if not provided in the metadata file. (#815)
A floating version in project references causes a System.ArgumentException and breaks the generation process. (#814)
Fixes the same problem that 3.0.1 tried to fix, by returning to the 2.10.0 functionality of resolving the location of the dotnet executable.
Fixes the same problem that 3.0.1 tried to fix, by returning to the 2.10.0 functionality of resolving the location of the dotnet executable.
Fixed a bug where CycloneDX on Linux systems searched for the dotnet executable in the wrong location, throwing a System.ComponentModel.Win32Exception
Fixed a bug where CycloneDX on Linux systems searched for the dotnet executable in the wrong location, throwing a System.ComponentModel.Win32Exception [sic] right at the start.
The flag --disable-github-licenses is now deprecated and set as the default launch setting. If you want to enable GitHub license resolution, you must…
The flag --disable-github-licenses is now deprecated and set as the default launch setting. If you want to enable GitHub license resolution, you must activate it by setting -enable-github-licenses.
Generated SBOMs are now of CycloneDX-Version 1.5
The following arguments are deprecated and will be replaced soon:
-d is now replaced by -ed-r is now replaced by -rs-f is now replaced by -fn--out is now replaced by --outputThe argument -v has been removed directly.
-ipr or --include-project-references, which adds project references to the bom output.--output flag is not mandatory anymore but defaults to the working directory.--exclude-dev flag now also removes dev dependencies from the dependency graph.McMaster.Extensions.CommandLineUtils to System.CommandLine.@Matiszak made their first contribution in https://github.com/CycloneDX/cyclonedx-dotnet/pull/777
Add .NET 8 support
Thanks to Matiszak
Full Changelog: https://github.com/CycloneDX/cyclonedx-dotnet/compare/v2.9.0...v2.10.0
Updated several dependencies, including NuGet.Protocol v6.5.0, addressing a vulnerability (CVE-2023-29337).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.