@shopify/prettier-plugin-liquid
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 | missing-githead | AI (provenance): SLSA-attested CI publish; gitHead absence is a benign env change for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate Shopify org maintainer rotation on official package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org rotation; no takeover indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable plugin; dormancy normal, CI-attested release. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.10.3 | 2 / 9 | |
| 1.10.2 | 2 / 7 | |
| 1.10.0 | 2 / 7 | |
| 1.9.4 | 2 / 7 | |
| 1.9.3 | 2 / 7 | |
| 1.9.2 | 2 / 7 | |
| 1.9.1 | 2 / 7 | |
| 1.9.0 | 2 / 7 | |
| 1.8.3 | 2 / 7 | |
| 1.8.2 | 2 / 7 | |
| 1.8.1 | 2 / 7 | |
| 1.8.0 | 2 / 7 | |
| 1.7.2 | 2 / 7 | |
| 1.7.0 | 2 / 7 | |
| 1.6.3 | 2 / 7 | |
| 1.6.2 | 2 / 7 | |
| 1.6.1 | 2 / 7 | |
| 1.6.0 | 2 / 7 | |
| 1.5.2 | 2 / 7 | |
| 1.5.1 | 2 / 7 |
v1.10.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.