@prisma/studio-core 0.0.0-dev.202505021110

Modular Prisma Studio components

@prisma/studio-core@0.0.0-dev.202505021110 was published on 2025-05-02. Its manifest declares 24 runtime dependencies and 4 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @prisma/studio-core versions · Permanent reference to 0.0.0-dev.202505021110 · Latest release

Package specifications

Version0.0.0-dev.202505021110
License declarationISC
Published2025-05-02T11:10:10.574Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count24
Peer requirement count4
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size1265.54 KiB
Published file count38
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies105
Repository stars2233
Repository forks87

Install @prisma/studio-core 0.0.0-dev.202505021110

npm install @prisma/studio-core@0.0.0-dev.202505021110
pnpm add @prisma/studio-core@0.0.0-dev.202505021110
yarn add @prisma/studio-core@0.0.0-dev.202505021110

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies7/10 — dependency not pinned by hash detected -- score normalized to 7
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection1/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness