@azure/storage-queue
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard base64 decode of storage account key, not payload hiding. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Localhost IP is the well-known Azurite emulator dev connection string. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 12.31.0 | 12 / 18 | |
| 12.30.0 | 12 / 18 | |
| 12.29.0 | 12 / 18 | |
| 12.28.1 | 12 / 18 | |
| 12.28.0 | 12 / 14 | |
| 12.27.0 | 12 / 14 | |
| 12.26.0 | 11 / 31 | |
| 12.25.0 | 11 / 31 | |
| 12.24.0 | 11 / 34 | |
| 12.23.0 | 11 / 34 | |
| 12.22.0 | 11 / 34 | |
| 12.17.0 | 6 / 40 |
v12.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.