@prisma/dev — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

prismabotaqrlntylerhogarthankur-datta-007

Keywords

prismapostgresacceleratelocaldevelopmentdevtesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:valibot	AI (phantom-deps): Declared dep; phantom-dep heuristic fires on bundled packages.	ai	2026/06/01
source-diff	obfuscated-file:dist/engine-XP6YJ63T.js	AI (source-diff): tsup-bundled query-engine wrapper; readable imports, spawns prisma engine binary as expected.	ai	2026/05/31
source-diff	obfuscated-file:dist/accelerate-5FDEK4T6.js	AI (source-diff): tsup-bundled output for hono/valibot accelerate proxy; readable imports, no obfuscation.	ai	2026/05/31
phantom-deps	phantom-dep:@electric-sql/pglite	AI (phantom-deps): Runtime dep used via config/dynamic wiring; stable false positive for this package.	ai	2026/05/30
phantom-deps	phantom-dep:pglite-server	AI (phantom-deps): Referenced in config files as expected for this local Postgres dev-server package.	ai	2026/05/30
phantom-deps	phantom-dep:pathe	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:foreground-child	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:@hono/node-server	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:http-status-codes	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:pako	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:std-env	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:env-paths	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:proper-lockfile	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:@prisma/get-platform	AI (phantom-deps): Same-org dep; stable false positive for Prisma packages.	ai	2026/05/29
phantom-deps	phantom-dep:@electric-sql/pglite-tools	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:@electric-sql/pglite-socket	AI (phantom-deps): Declared runtime dep; bundled output pattern.	ai	2026/05/29
phantom-deps	phantom-dep:hono	AI (phantom-deps): Declared runtime dep; bundled ESM package may not show direct imports to static analyzer.	ai	2026/05/29
phantom-deps	phantom-dep:read-last-lines-ts	AI (phantom-deps): Package is a declared runtime dep used indirectly via bundled dist; phantom-dep heuristic is a false positive here.	ai	2026/05/29
source-diff	obfuscated-file:dist/accelerate-UHQZHRYG.js	AI (source-diff): Minified tsup bundle output with readable imports; not obfuscation. Stable for this package.	ai	2026/05/27
publish-pattern	dormant-publish	AI (publish-pattern): @prisma scoped package with 830 versions; dormancy is normal release cadence variation.	ai	2026/05/27
source-diff	obfuscated-file:dist/accelerate-EEKAFGN3.js	AI (source-diff): Minified ESM bundle from tsup; content is readable and matches declared deps. Normal for this package.	ai	2026/04/28
source-diff	obfuscated-file:dist/accelerate-ZET2GIPN.js	AI (source-diff): Minified ESM bundle output from tsup; readable imports confirm legitimate build artifact, not obfuscation.	ai	2026/04/28
source-diff	obfuscated-file:dist/accelerate-HABH6RJU.js	AI (source-diff): Standard tsup/esbuild bundle output; sample shows legitimate Prisma/Hono imports, not obfuscation.	ai	2026/04/28
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped @prisma package; Levenshtein match to 'ajv' is a false positive with no semantic relationship.	ai	2026/04/28

Versions (showing 29 of 29)

Version	Deps	Published
0.24.7	17 / 13	2026-04-20
0.24.6	17 / 13	2026-04-15
0.24.5	17 / 12	2026-04-06
0.24.4	17 / 12	2026-04-06
0.24.3	17 / 12	2026-03-26
0.22.2	17 / 12	2026-03-19
0.22.1	17 / 12	2026-03-19
0.22.0	17 / 12	2026-03-16
0.21.0	17 / 12	2026-03-16
0.20.0	17 / 10	2026-01-19
0.19.1	17 / 10	2025-12-24
0.19.0	17 / 10	2025-12-23
0.18.0	17 / 10	2025-12-17
0.17.0	17 / 10	2025-12-16
0.16.1	17 / 10	2025-12-15
0.16.0	17 / 10	2025-12-12
0.15.0	17 / 10	2025-11-28
0.14.0	17 / 10	2025-11-26
0.13.0	17 / 10	2025-11-13
0.12.0	18 / 10	2025-10-22
0.10.0	15 / 10	2025-06-18
0.9.0	17 / 10	2025-06-16
0.6.1	15 / 10	2025-06-06
0.5.0	16 / 9	2025-06-05
0.3.0	15 / 9	2025-05-27
0.1.1	8 / 7	2025-05-14
0.1.0	8 / 7	2025-05-14
0.0.2	4 / 5	2025-05-08
0.0.1	3 / 5	2025-05-06

v0.24.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.24.6

4 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH New obfuscated file: dist/accelerate-5FDEK4T6.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/engine-XP6YJ63T.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.22.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.1

2 findings

HIGH New obfuscated file: dist/accelerate-HABH6RJU.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

2 findings

HIGH New obfuscated file: dist/accelerate-HABH6RJU.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

2 findings

HIGH New obfuscated file: dist/accelerate-EEKAFGN3.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.1

2 findings

HIGH New obfuscated file: dist/accelerate-EEKAFGN3.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

2 findings

HIGH New obfuscated file: dist/accelerate-ZET2GIPN.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

2 findings

HIGH New obfuscated file: dist/accelerate-ZET2GIPN.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

2 findings

HIGH New obfuscated file: dist/accelerate-UHQZHRYG.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

2 findings

HIGH New obfuscated file: dist/accelerate-UHQZHRYG.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.