@lynx-js/web-core
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): Manual-to-CI/CD migration with SLSA attestation is a legitimate maintainer workflow change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org's CI/CD publishing migration, not a takeover. | ai | |
| phantom-deps | phantom-dep:@lynx-js/web-worker-runtime | AI (phantom-deps): Same-org scope; likely bundled/re-exported rather than directly imported. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lynx-js/web-mainthread-apis | AI (phantom-deps): Same-org scope; likely bundled/re-exported rather than directly imported. Stable false positive for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires in wasm-bindgen generated glue code; standard pattern for WASM JS interop, not obfuscation. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.22.1 | 3 / 12 | |
| 0.22.0 | 3 / 12 | |
| 0.21.1 | 3 / 11 | |
| 0.21.0 | 3 / 11 | |
| 0.20.4 | 3 / 11 | |
| 0.20.3 | 3 / 11 | |
| 0.20.2 | 3 / 11 | |
| 0.20.1 | 3 / 11 | |
| 0.20.0 | 3 / 11 | |
| 0.19.9 | 5 / 2 | |
| 0.19.8 | 5 / 2 | |
| 0.19.7 | 5 / 2 | |
| 0.19.6 | 5 / 2 | |
| 0.19.5 | 5 / 2 | |
| 0.19.4 | 5 / 2 | |
| 0.19.3 | 5 / 2 | |
| 0.19.2 | 5 / 2 | |
| 0.19.1 | 5 / 2 | |
| 0.19.0 | 5 / 2 | |
| 0.18.4 | 5 / 2 | |
| 0.18.3 | 5 / 2 | |
| 0.18.2 | 5 / 2 | |
| 0.18.1 | 5 / 2 | |
| 0.18.0 | 5 / 2 | |
| 0.17.2 | 5 / 2 | |
| 0.17.1 | 5 / 2 | |
| 0.17.0 | 5 / 2 | |
| 0.16.1 | 5 / 2 | |
| 0.16.0 | 5 / 2 | |
| 0.15.7 | 5 / 2 | |
| 0.15.6 | 5 / 2 | |
| 0.15.5 | 5 / 2 | |
| 0.15.4 | 5 / 2 | |
| 0.15.3 | 5 / 2 | |
| 0.15.2 | 5 / 2 | |
| 0.15.1 | 5 / 2 | |
| 0.15.0 | 5 / 2 | |
| 0.14.2 | 5 / 2 | |
| 0.14.1 | 5 / 2 | |
| 0.14.0 | 5 / 2 | |
| 0.13.5 | 5 / 2 | |
| 0.13.4 | 5 / 2 | |
| 0.13.3 | 5 / 2 | |
| 0.13.2 | 5 / 2 | |
| 0.13.1 | 5 / 2 | |
| 0.13.0 | 5 / 2 | |
| 0.12.0 | 4 / 2 | |
| 0.11.0 | 4 / 2 | |
| 0.10.1 | 4 / 2 | |
| 0.10.0 | 4 / 2 | |
| 0.9.1 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.8.0 | 3 / 2 | |
| 0.7.1 | 3 / 2 | |
| 0.7.0 | 3 / 2 |
v0.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.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.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-25. 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.18.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-12. 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.17.2
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. 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.17.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-27. 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.17.0
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.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.