← Home

@lynx-example/lynx-ui-list

npm Repository Homepage

Example app demonstrating List usage in lynx-ui

8
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

huxprosevensever

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; consistent with legitimate org-level CI migration. ai
maintainer-change maintainer-added AI (maintainer-change): huxpro is a known contributor in the lynx-family org; addition consistent with legitimate maintainer onboarding. ai
phantom-deps phantom-dep:@lynx-js/react AI (phantom-deps): Example app; deps referenced in build config files, not direct imports — stable false positive for this package. ai
phantom-deps phantom-dep:@lynx-js/lynx-ui AI (phantom-deps): Example app; deps referenced in build config files, not direct imports — stable false positive for this package. ai
phantom-deps phantom-dep:@lynx-js/luna-styles AI (phantom-deps): Declared in config files as documented; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.8 3 / 5
0.0.7 3 / 5
0.0.6 3 / 5
0.0.5 3 / 5
0.0.4 3 / 5
0.0.3 3 / 5
0.0.2 3 / 5
0.0.1 3 / 5

v0.0.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.3

2 findings
HIGH Publisher changed: sevensever → GitHub Actions (on 2026-04-10) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 findings
HIGH Publisher changed: sevensever → GitHub Actions (on 2026-04-08) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.