@lynx-js/template-webpack-plugin
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation from official lynx-family org repo; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainers removed as part of migration to automated GitHub Actions publishing; consistent with org-level CI/CD transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is a known legitimate pattern; SLSA provenance corroborates integrity. | ai | |
| dependencies | unvetted-dep:@lynx-js/tasm | AI (dependencies): Same-org monorepo dependency (@lynx-family/lynx-stack); stable internal dep across versions. | ai | |
| phantom-deps | phantom-dep:css-tree | AI (phantom-deps): css-tree is explicitly declared in dependencies; phantom-dep heuristic misfires here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 9 / 8 | |
| 0.13.0 | 9 / 8 | |
| 0.12.2 | 9 / 7 | |
| 0.12.1 | 9 / 7 | |
| 0.12.0 | 9 / 7 | |
| 0.11.2 | 9 / 8 | |
| 0.11.1 | 9 / 8 | |
| 0.11.0 | 8 / 8 | |
| 0.10.9 | 7 / 7 | |
| 0.10.8 | 7 / 7 | |
| 0.10.7 | 7 / 7 | |
| 0.10.6 | 7 / 7 | |
| 0.10.4 | 6 / 8 | |
| 0.10.3 | 6 / 8 | |
| 0.10.2 | 6 / 8 | |
| 0.10.1 | 6 / 7 | |
| 0.10.0 | 6 / 7 | |
| 0.9.2 | 6 / 6 | |
| 0.9.1 | 6 / 6 | |
| 0.9.0 | 6 / 6 | |
| 0.8.6 | 6 / 6 | |
| 0.8.5 | 6 / 6 | |
| 0.8.4 | 6 / 6 | |
| 0.8.3 | 6 / 6 | |
| 0.8.2 | 6 / 6 | |
| 0.8.1 | 6 / 6 | |
| 0.8.0 | 6 / 6 | |
| 0.7.2 | 6 / 6 | |
| 0.7.1 | 6 / 6 | |
| 0.7.0 | 6 / 6 | |
| 0.6.11 | 6 / 6 | |
| 0.6.10 | 6 / 6 | |
| 0.6.9 | 6 / 6 | |
| 0.6.8 | 6 / 6 | |
| 0.6.7 | 6 / 6 | |
| 0.6.6 | 6 / 6 | |
| 0.6.5 | 6 / 6 | |
| 0.6.4 | 6 / 5 | |
| 0.6.3 | 6 / 5 |
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.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.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.