@open-keystone/adapter-prisma
KeystoneJS Prisma Database Adapter
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreads process.env to pass DATABASE_URL to prisma CLI — standard adapter pattern, not exfiltration. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync used only to invoke prisma CLI binary; no user-controlled input in the command. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads generated Prisma client from a known, adapter-controlled path; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): prisma is a CLI tool invoked via execSync, not imported directly; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:@prisma/client | AI (phantom-deps): Loaded dynamically via require(this.clientPath) after generation; phantom-dep is a false positive. | ai | |
| phantom-deps | phantom-dep:@prisma/internals | AI (phantom-deps): Used in config/schema generation logic; phantom-dep heuristic misses indirect usage patterns. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.0.32 | 7 / 0 | |
| 4.0.31 | 7 / 0 | |
| 4.0.30 | 7 / 0 | |
| 4.0.17 | 7 / 0 | |
| 4.0.16 | 7 / 0 | |
| 4.0.15 | 7 / 0 | |
| 4.0.14 | 7 / 0 | |
| 4.0.13 | 7 / 0 | |
| 4.0.12 | 7 / 0 | |
| 4.0.11 | 7 / 0 | |
| 4.0.10 | 7 / 0 | |
| 4.0.9 | 7 / 0 | |
| 4.0.8 | 7 / 0 | |
| 4.0.7 | 7 / 0 | |
| 4.0.6 | 7 / 0 | |
| 4.0.5 | 7 / 0 | |
| 4.0.4 | 7 / 0 | |
| 4.0.3 | 7 / 0 | |
| 4.0.2 | 7 / 0 | |
| 4.0.1 | 7 / 0 | |
| 4.0.0 | 7 / 0 |
v4.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.30
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/open-condo-software/open-keystone.git#main/blob/e5d192a00c57c04aa48ddf26af26186ecb775fb2/lib/adapter-prisma.js#L85 83 | 84 | return execSync(`${bin} ${cmd} --schema ${this.schemaPath}`, { > 85 | env: { ...process.env, DATABASE_URL: this._url() }, 86 | encoding: 'utf-8', 87 | });
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.17
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/keystonejs/keystone-5.git#main/blob/b8365e87d610bf4714e611af5e121e87a85433aa/lib/adapter-prisma.js#L55 53 | _runPrismaCmd(cmd) { 54 | return execSync(`npx prisma ${cmd} --schema ${this.schemaPath}`, { > 55 | env: { ...process.env, DATABASE_URL: this._url() }, 56 | encoding: 'utf-8', 57 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.