@tinacms/vercel-previews
⚠️ You must be a Vercel Enterprise customer for Visual Editing ⚠️
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 from human publisher to GitHub Actions CI is confirmed by SLSA provenance attestation; expected for tinacms monorepo. | ai | |
| phantom-deps | phantom-dep:tinacms | AI (phantom-deps): tinacms is a declared runtime dep in a monorepo package; indirect/config usage is expected. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.0.18 | 2 / 4 | |
| 0.0.17 | 2 / 4 | |
| 0.0.16 | 2 / 4 | |
| 0.0.15 | 2 / 4 | |
| 0.0.14 | 2 / 4 | |
| 0.0.13 | 2 / 4 | |
| 0.0.12 | 2 / 4 | |
| 0.0.11 | 2 / 4 | |
| 0.0.10 | 2 / 4 | |
| 0.0.9 | 2 / 4 | |
| 0.0.8 | 2 / 4 | |
| 0.0.7 | 2 / 4 | |
| 0.0.6 | 2 / 4 | |
| 0.0.5 | 2 / 4 | |
| 0.0.4 | 2 / 4 | |
| 0.0.3 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.