@adobe/spectrum-wc
Spectrum Web Components 2nd generation - rendering implementations
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@spectrum-web-components/core | AI (dependencies): First-party Adobe companion package from the same spectrum-web-components monorepo; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/components/badge/badge.js | AI (source-diff): Minified Lit CSS-in-JS template literal; standard build output for this Adobe Spectrum WC package. | ai | |
| source-diff | obfuscated-file:dist/components/button/button.js | AI (source-diff): Minified Lit CSS-in-JS template literal; standard build output for this Adobe Spectrum WC package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 0.1.0 is a major milestone release shipping compiled dist for many components; large file count is expected. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects new compiled component dist files; consistent with 0.1.0 release scope. | ai | |
| source-diff | obfuscated-file:dist/components/illustrated-message/illustrated-message.js | AI (source-diff): Minified Lit CSS-in-JS template literal; standard build output for this Adobe Spectrum WC package. | ai | |
| provenance | no-provenance | AI (provenance): Adobe org package; provenance absence is common and not a risk indicator here. | ai |
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.