@eeacms/volto-globalsearch
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall only patches an import in a sibling EEA package; no network calls, fully auditable string replacement. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in .eslintrc.js loads tsconfig for path aliases — standard build tooling pattern, not a runtime risk. | ai | |
| phantom-deps | phantom-dep:@eeacms/volto-searchlib | AI (phantom-deps): Listed as a Volto addon dependency in package.json addons field; same org scope, not a phantom dep concern. | ai |
v4.0.1
2 findingsScript: node -e "const fs=require('fs'); const path=require('path'); let file; try { file=path.join(path.dirname(require.resolve('@eeacms/volto-eea-chatbot/package.json')), 'src/ChatBlock/chat/AIMessage.tsx'); } catch (error) { process.exit(0); } const from=\"import visit from 'unist-util-visit';\"; const to=\"import { visit } from 'unist-util-visit';\"; const source=fs.readFileSync(file, 'utf8'); if (source.includes(from) && !source.includes(to)) { fs.writeFileSync(file, source.replace(from, to)); }"
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.