@plone-collective/volto-sentry No license 3 versions

@plone-collective/volto-sentry

npm Homepage

Versions

—

License

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

avoineasneridaghtimostollenwerkericofksuesspieronicollinileshgulia1

Keywords

volto-addonvoltoplonereact

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 reading package.json path at build time; not a runtime risk for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@sentry/browser	AI (phantom-deps): @sentry/browser is a declared runtime dependency used via config/integration files, not a direct import — stable false positive for this addon.	ai	2026/04/30

Versions (showing 3 of 3)

Version	Deps	Published
1.0.1	4 / 1	2026-06-04
1.0.0	4 / 1	2026-05-28
0.4.0	4 / 1	2025-10-01

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.4.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.