azure-devops-node-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in WebApi.js is used to decode a file path for certificate-based auth key lookup — a documented, legitimate pattern for this Azure DevOps API client. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature Microsoft SDK; long gaps between releases are expected. No material code changes vs prior version; no install script additions or suspicious payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): The vsonline maintainer's templated package names reflect Microsoft's Azure DevOps tooling ecosystem publishing pattern, not spam. This is a legitimate Microsoft package. | ai | |
| phantom-deps | phantom-dep:tunnel | AI (phantom-deps): tunnel is a legitimate runtime dependency for proxy support in this package; phantom detection is a false positive for this well-known Microsoft library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 15.1.3 | 2 / 9 | |
| 15.1.2 | 2 / 9 | |
| 15.1.1 | 2 / 9 | |
| 15.1.0 | 2 / 9 | |
| 15.0.0 | 2 / 9 |
v15.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.