@prisma-next/mongo-orm No license 15 versions

@prisma-next/mongo-orm

npm Repository Homepage

MongoDB ORM client for Prisma Next

15

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.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Published via GitHub Actions with SLSA/Sigstore attestation; missing gitHead is a minor metadata gap, not a supply chain risk for this package.	ai	2026/05/24
dependencies	unvetted-dep:@prisma-next/mongo-query-builder	AI (dependencies): Sibling package in the same @prisma-next monorepo, versioned identically; not an external third-party dep.	ai	2026/05/17
maintainer-change	maintainer-added	AI (maintainer-change): Publisher is GitHub Actions under the official prisma org with SLSA provenance; maintainer rotation is an internal team change.	ai	2026/05/17
maintainer-change	maintainer-removed	AI (maintainer-change): Same rationale — org-level CI publish with provenance attestation makes takeover scenario unlikely.	ai	2026/05/17
provenance	slsa-provenance	AI (provenance): Published from official Prisma org CI with Sigstore attestation; stable signal for this package.	ai	2026/05/17
publish-pattern	new-deps-added	AI (publish-pattern): New dep is a same-org sibling at matching version, consistent with monorepo coordinated releases.	ai	2026/05/17
dependencies	unvetted-dep:@prisma-next/mongo-core	AI (dependencies): workspace:* sibling in the prisma-next monorepo; not an external unvetted dependency.	ai	2026/05/17

Versions (showing 15 of 15)

Version	Deps	Published
0.12.0	7 / 12	2026-06-02
0.11.0	7 / 12	2026-05-22
0.10.0	7 / 12	2026-05-20
0.9.0	7 / 12	2026-05-20
0.8.0	7 / 12	2026-05-16
0.7.0	7 / 12	2026-05-15
0.6.1	7 / 12	2026-05-14
0.5.1	7 / 12	2026-05-12
0.5.0	7 / 12	2026-05-12
0.4.4	7 / 12	2026-05-07
0.4.3	7 / 12	2026-05-06
0.4.2	6 / 11	2026-04-27
0.4.1	6 / 11	2026-04-25
0.3.0	5 / 11	2026-04-16
0.0.1	3 / 6	2026-04-01

v0.12.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.11.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.10.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.9.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.8.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.7.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.6.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.5.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.5.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.4.4

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.