@truffle/preserve 0.1.0-preserves.4

Library for functionality for `truffle preserve` command

@truffle/preserve@0.1.0-preserves.4 was published on 2020-07-07. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All @truffle/preserve versions · Permanent reference to 0.1.0-preserves.4 · Latest release

Package specifications

Version0.1.0-preserves.4
License declarationMIT
Published2020-07-07T03:24:33.170Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size77.07 KiB
Published file count56
Package typeNot declared
ES module entryNot declared
Default entrydist/lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies15
Repository stars13904
Repository forks2287

Install @truffle/preserve 0.1.0-preserves.4

npm install @truffle/preserve@0.1.0-preserves.4
pnpm add @truffle/preserve@0.1.0-preserves.4
yarn add @truffle/preserve@0.1.0-preserves.4

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.

Code-Review6/10 — Found 4/6 approved changesets -- score normalized to 6
Maintained0/10 — project is archived
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
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
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected
Fuzzing10/10 — project is fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness