@equinor/eds-core-react No license 17 versions

@equinor/eds-core-react

npm Repository Homepage

17

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

oddverneschibuzormembuthalsethfridaerdal

Keywords

edsdesign systemequinorreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation; legitimate pipeline migration for this org.	ai	2026/05/30
provenance	missing-githead	AI (provenance): Consistent with CI/CD pipeline change; SLSA attestation provides stronger commit linkage than gitHead field.	ai	2026/05/30
provenance	no-provenance	AI (provenance): Long-established package with consistent publish history; lack of provenance is not a risk signal here.	ai	2026/05/28
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): @babel/runtime is a transitive runtime dep loaded by convention in bundled output; stable false positive for this package.	ai	2026/05/28
dependencies	unvetted-dep:@equinor/eds-utils	AI (dependencies): First-party Equinor monorepo package; stable companion dep across all versions of eds-core-react.	ai	2026/05/28

Versions (showing 17 of 17)

Version	Deps	Published
2.6.1	13 / 43	2026-05-20
2.6.0	13 / 43	2026-05-20
2.5.0	13 / 40	2026-04-14
2.4.1	13 / 40	2026-04-08
2.4.0	13 / 40	2026-03-20
2.3.7	13 / 40	2026-02-25
2.3.6	13 / 40	2026-02-20
2.3.5	13 / 40	2026-02-11
2.3.4	13 / 40	2026-02-05
2.3.3	13 / 40	2026-02-03
2.3.2	13 / 40	2026-01-29
2.3.1	13 / 40	2026-01-29
2.3.0	13 / 40	2026-01-15
2.2.0	13 / 39	2025-12-12
2.1.0	13 / 39	2025-11-26
2.0.1	13 / 39	2025-11-13
2.0.0	13 / 39	2025-11-06

v2.6.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: fridaerdal → GitHub Actions (on 2026-05-20) provenance

This version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.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.

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.7

1 finding

LOW No provenance attestation provenance

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

v2.3.6

1 finding

LOW No provenance attestation provenance

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

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

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.

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.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.

v2.1.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.

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

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