@azure/app-configuration
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): Base64 decode of HMAC signing secret, standard Azure auth pattern not payload hiding. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a known Microsoft OSS automation account; consistent with Azure SDK publishing pipeline. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Azure SDK build tooling migration to tshy generates multiple dist dialects; large file count increase is structural, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by tshy dual-module output (browser, react-native, esm, commonjs variants) added in this release. | ai | |
| phantom-deps | phantom-dep:@azure/abort-controller | AI (phantom-deps): Azure SDK peer/framework dependency; stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.12.1 | 12 / 22 | |
| 1.12.0 | 12 / 22 | |
| 1.11.0 | 11 / 22 | |
| 1.10.0 | 11 / 22 | |
| 1.9.2 | 11 / 22 | |
| 1.9.1 | 11 / 16 | |
| 1.9.0 | 11 / 16 | |
| 1.8.0 | 11 / 16 | |
| 1.7.0 | 11 / 32 | |
| 1.6.1 | 11 / 32 | |
| 1.6.0 | 11 / 32 | |
| 1.5.0 | 11 / 39 | |
| 1.4.1 | 10 / 39 | |
| 1.3.1 | 7 / 46 | |
| 1.3.0 | 7 / 48 | |
| 1.2.0 | 6 / 48 | |
| 1.1.1 | 6 / 47 | |
| 1.1.0 | 6 / 48 | |
| 1.0.1 | 7 / 31 | |
| 1.0.0 | 7 / 31 |
v1.6.0
2 findingsThis version was published by a different npm account (microsoft1es) than the most recent previously approved version (azure-sdk) on 2024-04-10. It has since remained available on npm for 829 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.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
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.