← Home

@eeacms/volto-listing-block

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

demarantavoineatiberiuichimzotyaalecghicaeea-jenkinsrazvan.miuichimdavvalentinab25nileshgulia1

Keywords

volto-addonvoltoplonereact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Fires in .eslintrc.js dev config for tsconfig path resolution; not runtime code, stable false positive for this package. ai
phantom-deps phantom-dep:@eeacms/volto-widget-theme-picker AI (phantom-deps): Same org scope dep declared but not directly imported; consistent pattern for Volto addon peer deps. ai

Versions (showing 4 of 4)

Version Deps Published
10.0.2 5 / 8
10.0.1 5 / 8
10.0.0 5 / 8
9.1.1 5 / 8

v10.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.