@microsoft/sp-search-extensibility
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/sp-search-extensibility_none_8a61e7df0525eb7db921.js | AI (source-diff): Minified webpack bundle output, not obfuscation; standard SPFx build artifact. | ai | |
| source-diff | obfuscated-file:dist/sp-search-extensibility_none_eeee2acfd0363ff11610.js | AI (source-diff): Standard webpack-minified dist bundle, consistent with prior approved releases of this package. | ai | |
| source-diff | obfuscated-file:dist/sp-search-extensibility_none_e39efa8282d42ec3c93c.js | AI (source-diff): Standard webpack-bundled dist output from Microsoft's own build, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/sp-search-extensibility_none_468e09802668fb8e0996.js | AI (source-diff): Standard webpack-minified bundle output, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @swc/helpers is a well-known compiler helper dep, benign for SPFx packages. | ai | |
| source-diff | obfuscated-file:dist/sp-search-extensibility_none_bfd684902a3289cfba0b.js | AI (source-diff): Standard SPFx webpack bundle output; minified but not obfuscated — normal for this Microsoft package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is Microsoft's standard OSS release automation account; expected for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SPFx SDK packages routinely have minimal READMEs and no keywords; not spam. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit runtime dep for SWC-compiled output; stable pattern across SPFx packages. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.23.2 | 6 / 6 | |
| 1.23.1 | 6 / 6 | |
| 1.23.0 | 6 / 6 | |
| 1.22.2 | 6 / 6 | |
| 1.22.1 | 6 / 6 | |
| 1.22.0 | 6 / 6 | |
| 1.21.1 | 6 / 6 | |
| 1.21.0 | 6 / 6 | |
| 1.20.0 | 5 / 6 | |
| 1.19.0 | 5 / 4 |
v1.23.2
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.23.1
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.21.0
3 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.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2025-04-23, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.20.0
3 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.
This version was published by a different npm account (microsoft1es) than the most recent previously approved version (odspnpm) on 2024-09-26, but microsoft1es is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.