@eeacms/volto-chatbot
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:uuid | AI (phantom-deps): uuid is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@plone-collective/volto-sentry | AI (phantom-deps): Listed as runtime dependency; used as a Volto addon via config, not direct import — stable false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 13 / 10 | |
| 2.0.2 | 13 / 10 | |
| 2.0.1 | 13 / 10 | |
| 2.0.0 | 13 / 10 | |
| 1.0.8 | 13 / 18 | |
| 1.0.7 | 13 / 18 | |
| 1.0.6 | 13 / 18 | |
| 1.0.5 | 13 / 18 | |
| 1.0.4 | 13 / 18 | |
| 1.0.3 | 13 / 18 | |
| 1.0.2 | 13 / 18 | |
| 1.0.1 | 13 / 18 | |
| 1.0.0 | 13 / 18 | |
| 0.6.4 | 13 / 10 | |
| 0.6.3 | 13 / 10 | |
| 0.6.2 | 13 / 10 |
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.