← Home

@equinor/fusion-wc-person

A web component library for person-related UI elements

32
Versions
ISC
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

_odin_nogglingseikeland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 32 of 32)

Version Deps Published
3.5.5 12 / 4
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
3.1.8 13 / 4
3.1.7 13 / 4
3.1.6 13 / 4
3.1.5 13 / 4
3.1.4 13 / 4
3.1.3 13 / 4
3.1.2 13 / 4
3.1.1 14 / 4
3.1.0 14 / 4
3.0.6 14 / 4
3.0.5 14 / 4
3.0.4 14 / 4
3.0.3 14 / 4
3.0.2 14 / 4
3.0.1 14 / 4
3.0.0 14 / 4

v3.1.8

1 finding
INFO No provenance attestation provenance

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

v3.1.7

1 finding
INFO No provenance attestation provenance

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

v3.1.6

1 finding
INFO No provenance attestation provenance

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

v3.1.5

1 finding
INFO No provenance attestation provenance

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

v3.1.4

1 finding
INFO No provenance attestation provenance

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

v3.1.3

1 finding
INFO No provenance attestation provenance

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

v3.1.2

1 finding
INFO No provenance attestation provenance

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

v3.1.1

1 finding
INFO No provenance attestation provenance

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

v3.1.0

1 finding
INFO No provenance attestation provenance

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

v3.0.6

1 finding
INFO No provenance attestation provenance

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

v3.0.5

1 finding
INFO No provenance attestation provenance

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

v3.0.4

1 finding
INFO No provenance attestation provenance

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

v3.0.3

1 finding
INFO No provenance attestation provenance

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

v3.0.2

1 finding
INFO No provenance attestation provenance

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

v3.0.1

1 finding
INFO No provenance attestation provenance

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

v3.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.