sugar

A Javascript utility library for working with native objects.

sugar@2.0.6 was published on 2018-12-05. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 0.8.23.

All sugar versions · Permanent reference to 2.0.6

Package specifications

Version2.0.6
License declarationMIT
Published2018-12-05T14:21:21.177Z
Node.js requirement>= 0.8.23
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2010.04 KiB
Published file count886
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars4501
Repository forks303

Install sugar 2.0.6

npm install sugar@2.0.6
pnpm add sugar@2.0.6
yarn add sugar@2.0.6

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-Review0/10 — Found 1/29 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness