@lynx-example/lynx-ui-radio-group
Example app demonstrating RadioGroup usage in lynx-ui
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate for lynx-family org packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): huxpro added as maintainer aligns with lynx-family org; no malicious indicators. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Build-time/config usage pattern for this example app; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lynx-js/react | AI (phantom-deps): Build-time/config usage pattern for this example app; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lynx-js/lynx-ui | AI (phantom-deps): Build-time/config usage pattern for this example app; stable false positive. | ai | |
| phantom-deps | phantom-dep:@lynx-js/luna-styles | AI (phantom-deps): luna-styles is declared as a runtime dep and referenced in config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 4 / 5 | |
| 0.0.9 | 4 / 5 | |
| 0.0.8 | 4 / 5 | |
| 0.0.7 | 4 / 5 | |
| 0.0.6 | 4 / 5 | |
| 0.0.5 | 4 / 5 | |
| 0.0.4 | 4 / 5 | |
| 0.0.3 | 4 / 5 | |
| 0.0.2 | 4 / 5 | |
| 0.0.1 | 4 / 5 |
v0.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.