@azure/arm-resources-subscriptions
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
azure-sdkmicrosoft1es
Keywords
nodeazuretypescriptbrowserisomorphic
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Microsoft consolidated Azure SDK publishing under microsoft1es; this transition is consistent across many Azure packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is the known Microsoft 1ES publishing account for Azure SDK packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects infrequent updates to this stable ARM SDK, not account takeover. | ai |
v2.1.1
2 findings
HIGH
Publisher changed: azure-sdk → microsoft1es (on 2025-08-22)
provenance
This version was published by a different npm account than previous versions on 2025-08-22. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.