@tinacms/scripts
This package provides the `tinacms-scripts` bin with the following commands:
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sucrase/jest-plugin | AI (dependencies): @sucrase/jest-plugin is a legitimate, widely-used jest transform; stable dependency for this build-tooling package. | ai | |
| phantom-deps | phantom-dep:tsup | AI (phantom-deps): tsup is a build tool invoked via CLI/config, not imported directly; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript used as a build-time tool via config, not directly imported; stable FP. | ai | |
| phantom-deps | phantom-dep:@sucrase/jest-plugin | AI (phantom-deps): Used as a Jest transform via config reference, not a direct import; stable FP for this build-scripts package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 9 / 3 | |
| 1.6.1 | 9 / 3 | |
| 1.6.0 | 10 / 3 | |
| 1.5.0 | 10 / 3 | |
| 1.4.2 | 10 / 3 | |
| 1.4.1 | 10 / 2 | |
| 1.4.0 | 10 / 2 | |
| 1.3.5 | 10 / 2 | |
| 1.3.4 | 10 / 0 | |
| 1.3.3 | 10 / 0 | |
| 1.3.2 | 9 / 0 | |
| 1.3.1 | 9 / 0 | |
| 1.3.0 | 9 / 0 | |
| 1.2.3 | 9 / 0 | |
| 1.2.2 | 9 / 0 | |
| 1.2.1 | 9 / 0 | |
| 1.2.0 | 9 / 0 | |
| 1.1.6 | 9 / 0 | |
| 1.1.5 | 9 / 0 |
v1.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (wicksipedia) on 2026-02-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wicksipedia) than the most recent previously approved version (jeffsee55) on 2024-09-30, but wicksipedia is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.