@parcel/optimizer-data-url 2.0.0-nightly.374

@parcel/optimizer-data-url@2.0.0-nightly.374 was published on 2020-08-19. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @parcel/optimizer-data-url versions · Permanent reference to 2.0.0-nightly.374 · Latest release

Package specifications

Version2.0.0-nightly.374
License declarationMIT
Published2020-08-19T00:14:36.556Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.12 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entrylib/DataURLOptimizer.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies79
Repository stars44007
Repository forks2303

Install @parcel/optimizer-data-url 2.0.0-nightly.374

npm install @parcel/optimizer-data-url@2.0.0-nightly.374
pnpm add @parcel/optimizer-data-url@2.0.0-nightly.374
yarn add @parcel/optimizer-data-url@2.0.0-nightly.374

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 1 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review1/10 — Found 3/28 approved changesets -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Binary-Artifacts5/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness