@microsoft/sp-lodash-subset
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-lodash-subset_25a86407e39cabb0157a.js | AI (source-diff): Standard minified lodash bundle output from Microsoft SPFx build pipeline; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/sp-lodash-subset_90044476422a825ce2cb.js | AI (source-diff): Standard SPFx AMD-format minified lodash bundle; consistent with this package's build pipeline across all versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Microsoft SPFx versioned release; publisher has strong track record with 3773 approved packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Implicit runtime dependency for TypeScript transpilation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Implicit runtime dependency for SWC transpilation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Type definitions loaded by convention; stable for TypeScript utility library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 3 / 10 | |
| 1.22.2 | 3 / 10 | |
| 1.22.1 | 3 / 10 | |
| 1.22.0 | 3 / 10 | |
| 1.21.1 | 3 / 11 |
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
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.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.