@azure/core-sse
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 1 / 24 | |
| 2.3.0 | 1 / 19 | |
| 2.2.0 | 1 / 19 | |
| 2.1.3 | 1 / 20 | |
| 2.1.2 | 1 / 15 | |
| 2.1.1 | 1 / 15 | |
| 2.1.0 | 1 / 15 | |
| 2.0.0 | 1 / 29 |
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
2 findingsThis version was published by a different npm account (microsoft1es) than the most recent previously approved version (azure-sdk) on 2024-04-11. It has since remained available on npm for 833 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.