@codesandbox/sandpack-client 0.1.1

A bundler that completely works in the browser and takes advantage of it.

@codesandbox/sandpack-client@0.1.1 was published on 2021-07-06. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @codesandbox/sandpack-client versions · Permanent reference to 0.1.1 · Latest release

Package specifications

Version0.1.1
License declarationGPL-2.0
Published2021-07-06T09:35:56.344Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size106071.09 KiB
Published file count557
Package typeNot declared
ES module entryesm/index.js
Default entrydist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies8
Repository stars6257
Repository forks484

Install @codesandbox/sandpack-client 0.1.1

npm install @codesandbox/sandpack-client@0.1.1
pnpm add @codesandbox/sandpack-client@0.1.1
yarn add @codesandbox/sandpack-client@0.1.1

Runtime dependencies

Peer requirements

  • None declared

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.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review3/10 — Found 8/25 approved changesets -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
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-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness