@microsoft/sp-http
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/sp-http_none_644fd2125765ae56f7fa.js | AI (source-diff): Standard webpack bundle for SPFx; minified output is expected for this Microsoft package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is Microsoft's release automation account; consistent with org-wide publishing practices. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit SWC runtime dependency; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Microsoft SPFx packages consistently lack keywords/code-block READMEs; not a spam indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 6 / 4 | |
| 1.22.2 | 6 / 4 | |
| 1.22.1 | 6 / 4 | |
| 1.22.0 | 6 / 4 | |
| 1.21.1 | 6 / 4 |
v1.23.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.