@brad-frost-web/eddie-web-components
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 | large-new-source-files | AI (source-diff): New CDN build target added; large number of new files is expected for a component library adding a second build output. | ai | |
| source-diff | obfuscated-file:cdn/components/inline-checkbox/inline-checkbox.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/layout/layout.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/black-friday-modal/black-friday-modal.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/button/button.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/checkbox-field-item/checkbox-field-item.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/counter/counter.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/file-upload/file-upload.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/grid/grid.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/heading/heading.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:cdn/components/icon/icon.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:components/icon.js | AI (source-diff): Minified Vite/Lit build output with inlined CSS; standard web component bundle pattern. | ai | |
| source-diff | obfuscated-file:components/black-friday-modal/black-friday-modal.js | AI (source-diff): Vite-minified CSS-in-JS bundle for a Lit component; long lines are inlined CSS, not obfuscation. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is a direct runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.31.0 | 3 / 26 | |
| 0.30.0 | 3 / 26 | |
| 0.29.0 | 3 / 26 | |
| 0.28.0 | 3 / 26 | |
| 0.27.0 | 3 / 26 | |
| 0.26.0 | 3 / 26 | |
| 0.25.0 | 3 / 26 | |
| 0.20.0 | 3 / 26 | |
| 0.19.5 | 3 / 26 | |
| 0.19.1 | 3 / 26 | |
| 0.17.0 | 3 / 26 | |
| 0.16.0 | 3 / 26 | |
| 0.15.0 | 3 / 26 | |
| 0.14.0 | 3 / 26 | |
| 0.13.0 | 3 / 26 | |
| 0.12.0 | 3 / 26 | |
| 0.11.0 | 3 / 26 | |
| 0.10.0 | 3 / 26 | |
| 0.9.0 | 3 / 26 | |
| 0.8.0 | 3 / 26 | |
| 0.7.0 | 3 / 26 | |
| 0.6.0 | 3 / 26 | |
| 0.5.0 | 3 / 26 | |
| 0.4.0 | 3 / 26 | |
| 0.3.0 | 3 / 26 | |
| 0.2.0 | 3 / 26 | |
| 0.1.0 | 3 / 26 |
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.5
13 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.
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.
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.
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.
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.
Newly 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.
v0.19.1
13 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
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.
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.
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.
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.
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.
Newly 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.
v0.17.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.
v0.16.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.
v0.15.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.
v0.14.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.
v0.13.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.
v0.12.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.
v0.11.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.
v0.10.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.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.