@eeacms/volto-eea-design-system No license 25 versions

@eeacms/volto-eea-design-system

npm Repository Homepage

25

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.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Fires in .eslintrc.js for tsconfig path resolution — dev tooling, not runtime code.	ai	2026/04/30
phantom-deps	phantom-dep:@eeacms/volto-corsproxy	AI (phantom-deps): Listed in addons array in package.json; phantom-dep heuristic is a false positive here.	ai	2026/04/30
phantom-deps	phantom-dep:remixicon	AI (phantom-deps): Icon font referenced via CSS/config, not JS imports; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@fontsource/roboto	AI (phantom-deps): Font package referenced via config/CSS, not JS imports; stable false positive.	ai	2026/04/30
phantom-deps	phantom-dep:react-lazy-load-image-component	AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package.	ai	2026/04/30

Versions (showing 25 of 25)

Version	Deps	Published
1.60.6	7 / 9	2026-06-06
1.60.5	7 / 9	2026-05-26
1.60.4	7 / 9	2026-05-21
1.60.3	7 / 9	2026-05-12
1.60.2	7 / 9	2026-04-22
1.60.1	7 / 9	2026-04-17
1.60.0	7 / 9	2026-04-17
1.50.2	7 / 9	2026-04-09
1.50.1	7 / 9	2026-04-07
1.50.0	7 / 9	2026-03-25
1.40.3	7 / 9	2026-02-11
1.40.2	7 / 9	2025-12-08
1.40.1	7 / 9	2025-12-04
1.40.0	7 / 9	2025-11-04
1.39.1	7 / 9	2025-09-22
1.39.0	7 / 8	2025-08-20
1.38.3	7 / 8	2025-07-31
1.38.2	7 / 8	2025-07-30
1.38.1	7 / 8	2025-07-28
1.38.0	7 / 8	2025-07-15
1.37.2	7 / 8	2025-07-02
1.37.1	7 / 8	2025-06-25
1.37.0	7 / 8	2025-06-06
1.36.6	7 / 8	2025-05-07
1.36.5	7 / 8	2025-05-07

v1.60.6

1 finding

LOW No provenance attestation provenance

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

v1.60.5

1 finding

LOW No provenance attestation provenance

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

v1.60.4

1 finding

LOW No provenance attestation provenance

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

v1.60.3

1 finding

LOW No provenance attestation provenance

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

v1.60.2

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.

v1.60.1

1 finding

LOW No provenance attestation provenance

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

v1.60.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.

v1.50.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.

v1.50.0

1 finding

LOW No provenance attestation provenance

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

v1.40.3

1 finding

LOW No provenance attestation provenance

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

v1.40.2

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.

v1.40.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.

v1.40.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.

v1.39.1

1 finding

LOW No provenance attestation provenance

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

v1.39.0

1 finding

LOW No provenance attestation provenance

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

v1.38.3

1 finding

LOW No provenance attestation provenance

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

v1.38.2

1 finding

LOW No provenance attestation provenance

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

v1.38.1

1 finding

LOW No provenance attestation provenance

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

v1.38.0

1 finding

LOW No provenance attestation provenance

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

v1.37.2

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.

v1.37.1

1 finding

LOW No provenance attestation provenance

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

v1.37.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.

v1.36.6

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.

v1.36.5

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.