@microsoft/sp-listview-extensibility
SharePoint Framework developer support for customizing the list view
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-listview-extensibility_none_32211638f8dca1a8efaa.js | AI (source-diff): Standard webpack bundle for Microsoft SPFx package; content is readable SPFx extension code, not malicious obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SDK sub-package; sparse README/keywords is normal for Microsoft SPFx component libraries. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit transitive dep for SWC-compiled output; stable pattern for this package family. | 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.