← Home

@lynx-js/template-webpack-plugin-canary

npm Repository

Simplifies creation of Lynx template files to serve your webpack bundles

39
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

colinaaa

Keywords

webpackLynx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Maintainers removed as part of transition to GitHub Actions CI/CD publishing; consistent with org-level automation. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is backed by SLSA provenance attestation; consistent with org-level CI/CD migration. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI/CD with Sigstore attestation; stable supply chain signal. ai
phantom-deps phantom-dep:css-tree AI (phantom-deps): css-tree is explicitly declared in package.json dependencies; phantom-dep is a false positive 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.5 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 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.13.0

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

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

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

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

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.6.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.6.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.6.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.6.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.6.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.6.3

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.