@prisma/cli-init

Version 0.8.0 • License MIT

One-Line Verdict

"Heavy install size detected. Review bloat risk."

npm install @prisma/cli-init

View Alternatives

60% Healy Score

Maintenance

Poor

Actively Maintained

Security

0 CVE History

No known CVEs.

Performance

6.0 MB

Critical Bloat: 6.0 MB

Community

6,148

Niche adoption.

How much does @prisma/cli-init slow down your app?

6.0 MB

Package Payload

21 Direct

Dependency Hell Risk: High chain complexity.

Cold-Start Impact

+89 ms

Estimated execution overhead on standard hardware.

Security Intelligence

Current Threat Level

Verified Stable

"No known vulnerabilities detected. Version 0.8.0 is stable."

Accuracy Protocol

Scanned against OSV.dev (Google Open Source) databases. Last Deep-Scan: 2026.

Alternatives Hub

Is @prisma/cli-init too heavy? Compare it with these industry standards:

@prisma/cli-init vs semver → @prisma/cli-init vs debug → @prisma/cli-init vs chalk → @prisma/cli-init vs tslib →

What is @prisma/cli-init?

"Init CLI for Prisma"

@prisma/cli-init is used to facilitate high-performance Node.js workflows. It provides a robust footprint of 6.0 MB on disk.

Installation Guide

# Install via NPM

npm install @prisma/cli-init

# Install via Yarn

yarn add @prisma/cli-init

Knowledge Base

Where can I find security audits for @prisma/cli-init?

You are currently viewing a proprietary security audit for @prisma/cli-init on PAudit. We aggregate global databases to provide a safety rating of 60/100.

How to use Node Package Manager to install @prisma/cli-init?

Run npm install @prisma/cli-init. This installs version 0.8.0 and adds 21 direct dependencies to your project.

Is @prisma/cli-init popular among Node developers?

Yes, @prisma/cli-init records 6,148 weekly downloads, making it a Niche adoption. part of the ecosystem.