@eeacms/volto-eea-website-theme
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 for tsconfig path resolution — dev tooling only, not runtime code. | ai | |
| phantom-deps | phantom-dep:@eeacms/volto-block-style | AI (phantom-deps): Same-org dep declared as peer/addon dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@eeacms/volto-group-block | AI (phantom-deps): Same-org dep declared as addon dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.3.7 | 6 / 10 | |
| 4.3.6 | 6 / 10 | |
| 4.3.5 | 6 / 10 | |
| 4.3.4 | 6 / 10 | |
| 4.3.3 | 6 / 10 | |
| 4.3.2 | 6 / 10 | |
| 4.3.1 | 6 / 10 | |
| 4.3.0 | 6 / 10 | |
| 4.2.0 | 6 / 10 | |
| 4.1.1 | 6 / 10 | |
| 4.1.0 | 6 / 10 | |
| 4.0.5 | 6 / 10 | |
| 4.0.4 | 6 / 10 | |
| 4.0.3 | 6 / 10 | |
| 3.19.1 | 6 / 10 | |
| 3.19.0 | 6 / 10 | |
| 3.18.1 | 6 / 10 | |
| 3.18.0 | 6 / 10 | |
| 3.17.1 | 6 / 10 | |
| 3.17.0 | 6 / 10 | |
| 3.16.0 | 6 / 10 | |
| 3.15.0 | 6 / 10 | |
| 3.14.1 | 6 / 10 | |
| 3.14.0 | 6 / 10 | |
| 3.13.0 | 6 / 9 | |
| 3.12.0 | 6 / 9 |
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.