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 56 of 156)
| Version | Deps | Published |
|---|---|---|
| 1.0.59 | 18 / 9 | |
| 1.0.58 | 18 / 9 | |
| 1.0.57 | 18 / 9 | |
| 1.0.56 | 18 / 9 | |
| 1.0.55 | 18 / 9 | |
| 1.0.54 | 18 / 9 | |
| 1.0.53 | 18 / 9 | |
| 1.0.51 | 18 / 9 | |
| 1.0.50 | 18 / 9 | |
| 1.0.49 | 18 / 9 | |
| 1.0.48 | 18 / 9 | |
| 1.0.46 | 18 / 9 | |
| 1.0.45 | 16 / 9 | |
| 1.0.44 | 16 / 9 | |
| 1.0.43 | 16 / 9 | |
| 1.0.42 | 16 / 8 | |
| 1.0.41 | 16 / 8 | |
| 1.0.40 | 16 / 8 | |
| 1.0.39 | 16 / 8 | |
| 1.0.38 | 16 / 8 | |
| 1.0.37 | 16 / 8 | |
| 1.0.36 | 16 / 8 | |
| 1.0.35 | 16 / 8 | |
| 1.0.34 | 16 / 8 | |
| 1.0.33 | 16 / 8 | |
| 1.0.30 | 16 / 8 | |
| 1.0.29 | 16 / 8 | |
| 1.0.28 | 16 / 8 | |
| 1.0.27 | 15 / 8 | |
| 1.0.26 | 15 / 8 | |
| 1.0.25 | 15 / 8 | |
| 1.0.24 | 15 / 8 | |
| 1.0.23 | 15 / 8 | |
| 1.0.22 | 15 / 8 | |
| 1.0.21 | 15 / 8 | |
| 1.0.20 | 15 / 8 | |
| 1.0.19 | 15 / 8 | |
| 1.0.18 | 15 / 8 | |
| 1.0.17 | 15 / 8 | |
| 1.0.14 | 15 / 8 | |
| 1.0.13 | 15 / 7 | |
| 1.0.8 | 15 / 7 | |
| 1.0.7 | 15 / 7 | |
| 1.0.6 | 15 / 7 | |
| 1.0.5 | 15 / 7 | |
| 1.0.3 | 15 / 7 | |
| 1.0.1 | 15 / 7 | |
| 1.0.0 | 15 / 7 | |
| 0.0.18 | 15 / 7 | |
| 0.0.17 | 15 / 7 | |
| 0.0.16 | 15 / 7 | |
| 0.0.11 | 15 / 7 | |
| 0.0.8 | 15 / 7 | |
| 0.0.4 | 15 / 7 | |
| 0.0.3 | 15 / 7 | |
| 0.0.1 | 14 / 7 |
v1.0.59
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.0.58
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.0.57
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.0.56
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.0.55
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.0.54
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.0.53
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.0.51
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.0.50
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.0.49
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.0.48
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.0.46
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.0.45
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.0.44
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.0.43
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.0.42
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.0.41
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.0.40
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.0.39
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.0.38
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.0.37
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.0.36
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.0.35
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.0.34
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.0.33
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.0.30
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.0.29
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.0.28
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.0.27
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.0.26
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.0.25
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.0.24
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.0.23
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.0.22
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.0.21
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.0.20
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.0.19
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.0.18
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.0.17
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.0.14
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.0.13
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.0.8
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.0.7
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.0.6
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.0.5
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.0.3
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.0.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.0.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.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.