@lynx-js/lynx-ui-lazy-component
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Explicitly declared placeholder package for namespace reservation; empty payload is intentional. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is appropriate for a placeholder/namespace-reservation package in the @lynx-js org. | ai | |
| provenance | slsa-provenance | AI (provenance): Published via GitHub Actions with Sigstore SLSA attestation; stable supply chain signal for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.133.1 | 1 / 5 | |
| 3.133.0 | 1 / 5 | |
| 3.131.0 | 1 / 5 | |
| 3.130.0 | 1 / 5 | |
| 0.0.0 | 0 / 0 |
v3.133.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.133.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.131.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.130.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.