cacha
My hunky-dory module
cacha@1.0.3 was published on 2015-11-15. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All cacha versions · Permanent reference to 1.0.3
Package specifications
| Version | 1.0.3 |
|---|---|
| License declaration | MIT |
| Published | 2015-11-15T07:53:27.370Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 9 |
| Repository stars | 21 |
| Repository forks | 0 |
Install cacha 1.0.3
npm install cacha@1.0.3 pnpm add cacha@1.0.3 yarn add cacha@1.0.3
Runtime dependencies
- home-or-tmp ^2.0.0
- mkdirp ^0.5.1
- path-is-absolute ^1.0.0
- pify ^2.3.0
- pinkie-promise ^2.0.0
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.
- home-or-tmp@2.0.0 — direct
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — direct
- os-homedir@1.0.2 — indirect
- os-tmpdir@1.0.2 — indirect
- path-is-absolute@1.0.1 — direct
- pify@2.3.0 — direct
- pinkie@2.0.4 — indirect
- pinkie-promise@2.0.1 — direct
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-Review | 0/10 — Found 0/16 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| Maintained | 0/10 — project is archived |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/cacha/1.0.3 — retrieved 2026-10-29T18:25:23.995Z
- https://api.deps.dev/v3/systems/npm/packages/cacha/versions/1.0.3 — retrieved 2026-10-29T18:25:23.937Z
- https://api.deps.dev/v3/systems/npm/packages/cacha/versions/1.0.3:dependencies — retrieved 2026-10-29T18:25:23.968Z
- https://api.deps.dev/v3/projects/github.com%2Ffloatdrop%2Fcacha — retrieved 2026-10-29T18:25:24.556Z