@effectify/prisma
A powerful Prisma generator that creates **Effect** services and layers from your Prisma schema, enabling seamless integration of Prisma with the Effect ecosystem.
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex pattern in minified Prisma runtime/client.js is a false positive from bundled code, not a payload. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Prisma generated client decodes WASM binary from base64; stable pattern across all Prisma client versions. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Declared dependency; used in Prisma adapter config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@prisma/adapter-better-sqlite3 | AI (phantom-deps): Declared dependency; used in Prisma adapter config, not direct imports. | ai | |
| phantom-deps | phantom-dep:@prisma/generator | AI (phantom-deps): Declared dependency; used in Prisma generator config, not direct imports. | ai | |
| phantom-deps | phantom-dep:kysely | AI (phantom-deps): Declared dependency; used in Prisma generator config, not direct imports. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present to compound it. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.1.12 | 6 / 19 | |
| 1.1.11 | 6 / 19 | |
| 1.1.10 | 6 / 19 | |
| 1.1.9 | 6 / 18 | |
| 1.1.8 | 6 / 18 | |
| 1.1.7 | 6 / 18 | |
| 1.1.6 | 6 / 18 | |
| 1.1.5 | 6 / 18 | |
| 1.1.4 | 6 / 18 | |
| 1.1.3 | 9 / 15 | |
| 1.1.2 | 9 / 15 | |
| 1.1.1 | 9 / 15 | |
| 1.1.0 | 9 / 15 | |
| 1.0.1 | 7 / 14 | |
| 1.0.0 | 7 / 14 | |
| 0.1.2 | 7 / 14 | |
| 0.1.1 | 11 / 13 |
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.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.
v0.1.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.