@prisma/compute-cli No license 21 versions

@prisma/compute-cli

npm Repository Homepage

Command-line interface for deploying and managing [Prisma Compute](https://www.prisma.io/compute) services.

21

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal Prisma CLI tool; sparse metadata is expected for early-stage org tooling, not a spam indicator.	ai	2026/05/06
phantom-deps	phantom-dep:zod	AI (phantom-deps): zod is declared as a runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:openapi-fetch	AI (phantom-deps): openapi-fetch is declared as a runtime dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/04/30

Versions (showing 21 of 21)

Version	Deps	Published
0.22.0	8 / 2	2026-06-03
0.21.0	8 / 2	2026-06-02
0.20.0	8 / 2	2026-05-29
0.19.0	8 / 2	2026-05-26
0.18.0	8 / 2	2026-05-21
0.17.0	8 / 2	2026-04-28
0.16.0	8 / 2	2026-04-22
0.15.0	8 / 2	2026-04-22
0.14.0	8 / 2	2026-04-10
0.13.0	8 / 2	2026-04-10
0.12.0	8 / 2	2026-04-10
0.11.0	8 / 2	2026-04-08
0.10.0	8 / 2	2026-04-07
0.9.0	8 / 2	2026-04-07
0.8.0	8 / 2	2026-04-07
0.7.0	8 / 2	2026-03-31
0.6.0	8 / 2	2026-03-30
0.5.0	8 / 2	2026-03-30
0.4.0	8 / 2	2026-03-30
0.3.0	8 / 2	2026-03-30
0.1.0	8 / 2	2026-03-26

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.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.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

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