← Home

@prisma-next/target-postgres

npm Repository Homepage

Postgres target pack for Prisma Next

5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tylerhogarthaqrlnwmadden-prisma

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@prisma-next/sql-operations AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for this package. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is used for pg/bytea codec serialization — expected for a Postgres type codec library. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used for runtime type introspection in enum-planning — idiomatic TypeScript codec pattern, not obfuscation. ai
phantom-deps phantom-dep:pathe AI (phantom-deps): pathe is declared in package.json dependencies; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@prisma-next/cli AI (phantom-deps): Org-scoped monorepo sibling; phantom-dep is a stable false positive for this package. ai
phantom-deps phantom-dep:@prisma-next/contract AI (phantom-deps): Org-scoped monorepo sibling; phantom-dep is a stable false positive for this package. ai
dependencies unvetted-dep:@prisma-next/family-sql AI (dependencies): Internal sibling package from the same prisma/prisma-next monorepo; expected dependency pattern. ai
dependencies unvetted-dep:@prisma-next/sql-runtime AI (dependencies): Internal sibling package from the same prisma/prisma-next monorepo; expected dependency pattern. ai

Versions (showing 5 of 5)

Version Deps Published
0.12.0 16 / 6
0.4.3 15 / 6
0.4.1 16 / 9
0.3.0 12 / 9
0.0.1 5 / 4

v0.12.0

2 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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.4.3

2 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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.4.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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.