@equinor/fusion-react-filter
component for Filtering data
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@equinor/fusion-react-styles | AI (dependencies): Internal Equinor ecosystem dependency; consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:@equinor/eds-tokens | AI (dependencies): First-party Equinor EDS design-system token package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-wc-chip | AI (dependencies): First-party Equinor Fusion web component; consistent with this package's ecosystem. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 6 / 5 | |
| 2.1.2 | 6 / 5 | |
| 2.1.1 | 6 / 5 | |
| 2.1.0 | 6 / 5 | |
| 2.0.3 | 5 / 5 | |
| 2.0.2 | 5 / 5 | |
| 2.0.1 | 5 / 5 | |
| 2.0.0 | 5 / 5 |
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.