prisma-yml
<a href="https://www.prismagraphql.com"><img src="https://imgur.com/HUu10rH.png" width="248" /></a>
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:yaml-ast-parser | AI (dependencies): yaml-ast-parser is a legitimate YAML AST parsing library used throughout the Prisma ecosystem; stable dependency for this package across many versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Prisma ecosystem package; missing description is a cosmetic issue with no security relevance for this well-known publisher. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected and not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:scuid | AI (phantom-deps): scuid is a benign unique ID generator; phantom dep status likely reflects compiled dist usage rather than direct source import. | ai | |
| phantom-deps | phantom-dep:yaml-ast-parser | AI (phantom-deps): yaml-ast-parser is a known YAML parsing library used in the Prisma ecosystem; phantom dep status reflects compiled dist usage. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Package has 859 versions with frequent automated releases; rapid publish cadence is normal for this project's CI/CD pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link density reflects legitimate Prisma/Graphcool ecosystem documentation; not a phishing link farm. Package has clear purpose, repo URL, and license. | ai |
Versions (showing 51 of 156)
| Version | Deps | Published |
|---|---|---|
| 1.34.12 | 18 / 9 | |
| 1.34.11 | 18 / 9 | |
| 1.34.10 | 18 / 9 | |
| 1.34.6 | 18 / 9 | |
| 1.34.3 | 18 / 9 | |
| 1.34.2 | 18 / 9 | |
| 1.34.1 | 18 / 9 | |
| 1.34.0 | 18 / 9 | |
| 1.33.0 | 18 / 9 | |
| 1.32.2 | 18 / 9 | |
| 1.32.1 | 18 / 9 | |
| 1.32.0 | 18 / 9 | |
| 1.31.2 | 18 / 9 | |
| 1.31.1 | 18 / 9 | |
| 1.31.0 | 18 / 9 | |
| 1.30.5 | 18 / 9 | |
| 1.30.3 | 18 / 9 | |
| 1.30.2 | 18 / 9 | |
| 1.30.1 | 18 / 9 | |
| 1.30.0 | 18 / 9 | |
| 1.29.2 | 18 / 9 | |
| 1.29.0 | 18 / 9 | |
| 1.28.5 | 18 / 9 | |
| 1.28.3 | 18 / 9 | |
| 1.28.2 | 18 / 9 | |
| 1.28.1 | 18 / 9 | |
| 1.28.0 | 18 / 9 | |
| 1.27.4 | 18 / 9 | |
| 1.27.3 | 18 / 9 | |
| 1.27.2 | 18 / 9 | |
| 1.27.1 | 18 / 9 | |
| 1.27.0 | 18 / 9 | |
| 1.26.2 | 18 / 9 | |
| 1.25.7 | 18 / 9 | |
| 1.25.5 | 18 / 9 | |
| 1.25.4 | 18 / 9 | |
| 1.25.3 | 18 / 9 | |
| 1.25.2 | 18 / 9 | |
| 1.25.1 | 18 / 9 | |
| 1.25.0 | 18 / 9 | |
| 1.24.0 | 18 / 9 | |
| 1.23.4 | 18 / 9 | |
| 1.23.3 | 18 / 9 | |
| 1.23.2 | 18 / 9 | |
| 1.23.1 | 18 / 9 | |
| 1.23.0 | 18 / 9 | |
| 1.22.2 | 18 / 9 | |
| 1.22.1 | 18 / 9 | |
| 1.22.0 | 18 / 9 | |
| 1.21.1 | 18 / 9 | |
| 1.21.0 | 18 / 9 |
v1.34.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.