@eeacms/volto-prefixpath
@eeacms/volto-prefixpath: Volto add-on
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 loading a jsconfig paths file — standard Volto add-on dev tooling, not a runtime concern. | ai | |
| phantom-deps | phantom-dep:@eeacms/volto-eea-design-system | AI (phantom-deps): Declared as a Volto add-on dependency in the addons field; same org scope, not a phantom dep in practice. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 1 / 9 | |
| 2.0.4 | 1 / 9 | |
| 2.0.3 | 1 / 9 | |
| 2.0.2 | 1 / 9 | |
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 9 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.