@azure/keyvault-common
Common internal functionality for all of the Azure Key Vault clients in the Azure SDK for JavaScript
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency from TypeScript transpilation; stable for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-auth | AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-client | AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@azure/core-tracing | AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@azure/abort-controller | AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; stable for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 8 / 13 | |
| 2.0.1 | 8 / 10 | |
| 2.0.0 | 8 / 13 | |
| 1.0.0 | 6 / 16 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.