@shopify/theme-check-docs-updater
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): CI-published Shopify package with SLSA attestation; gitHead absence is a benign publish-env change. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(path.resolve(__dirname,'../dist')) loads package's own build output, not arbitrary code. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 3.28.0 | 3 / 1 | |
| 3.27.0 | 3 / 1 | |
| 3.26.1 | 3 / 1 | |
| 3.26.0 | 3 / 1 | |
| 3.25.1 | 3 / 1 | |
| 3.25.0 | 3 / 1 | |
| 3.24.0 | 3 / 1 | |
| 3.23.0 | 3 / 1 | |
| 3.22.0 | 3 / 1 | |
| 3.21.0 | 3 / 1 | |
| 3.20.1 | 3 / 1 | |
| 3.20.0 | 3 / 1 | |
| 3.19.0 | 3 / 1 | |
| 3.18.1 | 3 / 1 | |
| 3.18.0 | 3 / 1 | |
| 3.17.1 | 3 / 1 | |
| 3.17.0 | 3 / 1 | |
| 3.16.1 | 3 / 1 | |
| 3.16.0 | 3 / 1 | |
| 3.15.1 | 3 / 1 | |
| 3.15.0 | 3 / 1 | |
| 3.14.1 | 3 / 1 | |
| 3.14.0 | 3 / 1 | |
| 3.13.1 | 3 / 1 | |
| 3.13.0 | 3 / 1 | |
| 3.12.0 | 3 / 1 | |
| 3.11.1 | 3 / 1 | |
| 3.11.0 | 3 / 1 | |
| 3.10.0 | 3 / 1 | |
| 3.9.0 | 3 / 1 | |
| 3.8.0 | 3 / 1 | |
| 3.7.2 | 3 / 1 | |
| 3.7.1 | 3 / 1 | |
| 3.6.1 | 3 / 1 | |
| 3.6.0 | 3 / 1 | |
| 3.5.0 | 3 / 1 | |
| 3.4.0 | 3 / 1 | |
| 3.3.0 | 3 / 1 | |
| 3.2.2 | 3 / 1 | |
| 3.2.1 | 3 / 1 | |
| 3.2.0 | 3 / 1 | |
| 3.1.0 | 3 / 1 | |
| 3.0.0 | 3 / 1 |
v3.28.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v3.27.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This 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.
v3.26.1
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.
v3.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.