@lynx-js/lynx-ui-button
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Intentional placeholder at 0.0.0 under a legitimate scoped namespace. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Explicitly declared placeholder package; empty payload and missing metadata are expected. | ai | |
| dependencies | unvetted-dep:@lynx-js/lynx-ui-common | AI (dependencies): Sibling package from the same lynx-family/lynx-ui monorepo; expected internal dependency. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.133.1 | 3 / 5 | |
| 3.133.0 | 2 / 5 | |
| 3.131.0 | 2 / 5 | |
| 3.130.0 | 2 / 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.