@eeacms/volto-cca-policy MIT 25 versions

@eeacms/volto-cca-policy

npm Repository Homepage

@eeacms/volto-cca-policy: Volto add-on

25

Versions

MIT

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.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@plone-collective/volto-rss-provider	AI (phantom-deps): Volto addon config reference pattern; not directly imported, consistent with other phantom deps in this package.	ai	2026/05/21
phantom-deps	phantom-dep:d3-array	AI (phantom-deps): Declared dependency used in config; stable pattern for this package.	ai	2026/05/10
phantom-deps	phantom-dep:@elastic/search-ui	AI (phantom-deps): Declared dependency used in config; stable pattern for this package.	ai	2026/05/10
phantom-deps	phantom-dep:@eeacms/volto-group-block	AI (phantom-deps): Declared dependency used in config; stable pattern for this package.	ai	2026/05/10
phantom-deps	phantom-dep:@eeacms/volto-slate-label	AI (phantom-deps): Declared dependency used in config; stable pattern for this package.	ai	2026/05/10
phantom-deps	phantom-dep:@eeacms/volto-searchlib	AI (phantom-deps): Declared dependency used in config; stable pattern for this package.	ai	2026/05/10
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is in .eslintrc.js to read tsconfig paths — dev config only, not runtime code.	ai	2026/04/29

Versions (showing 25 of 25)

Version	Deps	Published
1.0.0	18 / 11	2026-06-12
0.3.131	18 / 11	2026-06-08
0.3.129	18 / 11	2026-06-08
0.3.128	18 / 11	2026-06-03
0.3.127	18 / 11	2026-05-27
0.3.126	18 / 11	2026-05-26
0.3.125	18 / 11	2026-05-18
0.3.124	18 / 11	2026-05-12
0.3.123	18 / 11	2026-05-11
0.3.122	18 / 11	2026-05-08
0.3.121	18 / 11	2026-05-07
0.3.120	17 / 11	2026-04-30
0.3.119	17 / 11	2026-04-30
0.3.118	17 / 11	2026-04-28
0.3.117	17 / 11	2026-04-28
0.3.116	17 / 11	2026-04-27
0.3.115	17 / 11	2026-04-27
0.3.114	17 / 11	2026-04-16
0.3.113	17 / 11	2026-04-15
0.3.112	17 / 11	2026-04-14
0.3.111	17 / 11	2026-04-09
0.3.110	17 / 11	2026-04-08
0.3.109	17 / 11	2026-04-01
0.3.108	17 / 11	2026-03-31
0.3.107	17 / 11	2026-03-30

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.3.131

1 finding

LOW No provenance attestation provenance

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

v0.3.129

1 finding

LOW No provenance attestation provenance

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

v0.3.128

1 finding

LOW No provenance attestation provenance

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

v0.3.127

1 finding

LOW No provenance attestation provenance

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

v0.3.126

1 finding

LOW No provenance attestation provenance

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

v0.3.125

1 finding

LOW No provenance attestation provenance

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

v0.3.124

1 finding

LOW No provenance attestation provenance

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

v0.3.123

1 finding

LOW No provenance attestation provenance

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

v0.3.122

1 finding

LOW No provenance attestation provenance

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

v0.3.121

1 finding

LOW No provenance attestation provenance

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

v0.3.120

1 finding

LOW No provenance attestation provenance

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

v0.3.119

1 finding

LOW No provenance attestation provenance

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

v0.3.117

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.

v0.3.116

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.

v0.3.115

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.

v0.3.114

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.

v0.3.113

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.

v0.3.112

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.

v0.3.111

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.

v0.3.110

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.

v0.3.109

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.

v0.3.108

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.

v0.3.107

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.