@eeacms/volto-accordion-block
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in .eslintrc.js dev config only; not runtime code, no exploit path. | ai | |
| phantom-deps | phantom-dep:@eeacms/volto-widget-theme-picker | AI (phantom-deps): Same-org dependency declared in package.json; likely used transitively by Volto addon consumers. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 13.0.3 | 1 / 8 | |
| 13.0.2 | 1 / 8 | |
| 13.0.1 | 1 / 8 | |
| 13.0.0 | 1 / 8 | |
| 12.0.0 | 1 / 8 |
v13.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.