snappy 1.3.1

Nodejs bindings to Google's Snappy compression library

snappy@1.3.1 was published on 2013-02-26. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.4.5.

All snappy versions · Permanent reference to 1.3.1 · Latest release

Package specifications

Version1.3.1
License declarationNot declared
Published2013-02-26T21:59:42.850Z
Node.js requirement>= 0.4.5
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/snappy.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars214
Repository forks15

Install snappy 1.3.1

npm install snappy@1.3.1
pnpm add snappy@1.3.1
yarn add snappy@1.3.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.

Maintained10/10 — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 0/21 approved changesets -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness