@lynx-js/react-rsbuild-plugin-canary
A rsbuild plugin for ReactLynx
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Canary release pattern; empty entry point and minimal README are expected for this package family. | ai | |
| phantom-deps | phantom-dep:background-only | AI (phantom-deps): background-only is declared as a dep alias; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@lynx-js/use-sync-external-store | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a false positive. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Declared in dependencies; likely used transitively or in config — stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 9 / 18 | |
| 0.18.0 | 9 / 18 | |
| 0.17.2 | 9 / 18 | |
| 0.17.1 | 9 / 18 | |
| 0.17.0 | 9 / 18 | |
| 0.16.3 | 9 / 17 | |
| 0.16.2 | 9 / 17 | |
| 0.16.1 | 9 / 17 | |
| 0.14.0 | 8 / 17 | |
| 0.10.14 | 8 / 15 | |
| 0.10.13 | 8 / 15 | |
| 0.10.12 | 8 / 13 | |
| 0.10.11 | 8 / 14 | |
| 0.10.10 | 8 / 16 | |
| 0.10.9 | 8 / 16 | |
| 0.10.8 | 8 / 16 | |
| 0.10.7 | 8 / 16 | |
| 0.10.6 | 8 / 16 | |
| 0.10.5 | 8 / 16 | |
| 0.10.4 | 8 / 16 | |
| 0.10.3 | 8 / 16 | |
| 0.10.2 | 7 / 16 | |
| 0.10.1 | 7 / 16 | |
| 0.10.0 | 7 / 16 | |
| 0.9.10 | 8 / 15 | |
| 0.9.9 | 8 / 15 | |
| 0.9.8 | 8 / 15 | |
| 0.9.7 | 7 / 15 | |
| 0.9.6 | 7 / 15 | |
| 0.9.5 | 7 / 15 | |
| 0.9.4 | 7 / 14 | |
| 0.9.3 | 7 / 14 | |
| 0.9.2 | 7 / 14 | |
| 0.9.1 | 7 / 14 | |
| 0.9.0 | 7 / 14 |
v0.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.