@lynx-js/web-elements
It provides the custom-element implementation of Lynx Elements in Web.
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): Move to CI/CD publisher with SLSA attestation, not compromise indicator. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Expected artifact of switching to automated CI publishing. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-managed package with strong publisher track record; provenance unchanged. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; dormancy explained by project cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@lynx-js/web-elements-template | AI (dependencies): Same-org sibling package from lynx-family/lynx-stack; stable internal dependency. | ai | |
| dependencies | unvetted-dep:@lynx-js/web-elements-reactive | AI (dependencies): Same-org sibling package from lynx-family/lynx-stack; stable internal dependency. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established Markdown parser; its use is justified by the XMarkdown element in this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.12.7 | 2 / 8 | |
| 0.12.6 | 2 / 7 | |
| 0.12.5 | 2 / 7 | |
| 0.12.4 | 2 / 7 | |
| 0.12.3 | 2 / 7 | |
| 0.12.2 | 2 / 7 | |
| 0.12.1 | 2 / 7 | |
| 0.12.0 | 0 / 6 | |
| 0.11.3 | 0 / 6 | |
| 0.11.2 | 0 / 6 | |
| 0.11.1 | 0 / 6 | |
| 0.11.0 | 0 / 6 | |
| 0.10.1 | 0 / 6 | |
| 0.10.0 | 0 / 6 | |
| 0.9.0 | 2 / 1 | |
| 0.8.11 | 2 / 1 | |
| 0.8.10 | 2 / 1 | |
| 0.8.9 | 2 / 1 | |
| 0.8.8 | 2 / 1 | |
| 0.8.7 | 2 / 1 | |
| 0.8.6 | 2 / 1 | |
| 0.8.5 | 2 / 1 | |
| 0.8.4 | 2 / 1 | |
| 0.8.3 | 2 / 1 | |
| 0.8.2 | 2 / 1 | |
| 0.8.1 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.7 | 2 / 1 | |
| 0.7.6 | 2 / 1 | |
| 0.7.5 | 2 / 1 | |
| 0.7.4 | 2 / 1 | |
| 0.7.3 | 2 / 1 | |
| 0.7.2 | 2 / 1 | |
| 0.7.1 | 1 / 1 | |
| 0.7.0 | 1 / 1 | |
| 0.6.0 | 1 / 1 | |
| 0.5.4 | 1 / 1 | |
| 0.5.3 | 1 / 1 | |
| 0.5.2 | 1 / 1 | |
| 0.5.1 | 1 / 1 | |
| 0.5.0 | 1 / 1 | |
| 0.4.0 | 1 / 1 | |
| 0.3.0 | 1 / 1 | |
| 0.2.4 | 1 / 1 |
v0.12.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.7
2 findingsThis version was published by a different npm account than previous versions on 2025-09-21. 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.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.