@azure/arm-storage
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
amarzaveryvladbarosanveronicaggazure-sdkmicrosoft1esmicrosoft-oss-releases
Keywords
nodeazurecloudtypescriptbrowserisomorphic
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 499 versions; dormancy is an artifact of the diff baseline, not real inactivity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New Azure SDK core deps are first-party Microsoft packages consistent with SDK generation migration. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large file count reflects SDK codegen output across CJS/ESM/browser targets; expected for major version. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dep. | ai | |
| phantom-deps | phantom-dep:@azure/core-util | AI (phantom-deps): Framework-scoped Azure dep; used by generated code conventions. | ai |
v20.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.