@equinor/fusion-wc-person
A web component library for person-related UI elements
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package publishes via CI with Sigstore attestation; stable supply chain signal for this package. | ai | |
| phantom-deps | phantom-dep:@equinor/fusion-wc-badge | AI (phantom-deps): Same-org package declared as dep; likely used transitively or in types — stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate for this Equinor monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Long-established Equinor org package; lack of provenance is consistent across all versions and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-web-theme | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-skeleton | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@lit-labs/observers | AI (dependencies): Legitimate Lit Labs library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-searchable-dropdown | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-textinput | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-icon | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-list | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-button | AI (dependencies): Sibling @equinor package from same monorepo; stable dependency. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.5.4 | 12 / 4 | |
| 3.5.3 | 12 / 4 | |
| 3.5.2 | 12 / 4 | |
| 3.5.1 | 12 / 4 | |
| 3.5.0 | 12 / 4 | |
| 3.4.1 | 12 / 4 | |
| 3.4.0 | 12 / 4 | |
| 3.3.1 | 12 / 4 | |
| 3.3.0 | 14 / 4 | |
| 3.2.4 | 13 / 4 | |
| 3.2.3 | 13 / 4 | |
| 3.2.2 | 13 / 4 | |
| 3.2.1 | 13 / 4 | |
| 3.2.0 | 13 / 4 | |
| 3.1.9 | 13 / 4 |
v3.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.