nswag
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): NSwag ships .NET runtime binaries by design; this is the documented distribution mechanism for the CLI tool. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to spawn the .NET dotnet-nswag binary; core to the CLI wrapper's function. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 14.7.1 | 0 / 0 |
v14.7.1
2 findingsPackage contains compiled binaries that could be backdoors: • bin/binaries/Net100/dotnet-nswag.dll • bin/binaries/Net80/dotnet-nswag.dll • bin/binaries/Net90/dotnet-nswag.dll • bin/binaries/Net100/Fluid.dll • bin/binaries/Net80/Fluid.dll • bin/binaries/Net90/Fluid.dll • bin/binaries/Win/Fluid.dll • bin/binaries/Win/Microsoft.AspNetCore.Authentication.Abstractions.dll • bin/binaries/Win/Microsoft.AspNetCore.Authentication.Core.dll • bin/binaries/Win/Microsoft.AspNetCore.Authorization.dll ... and 259 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.