cachegoose 4.0.1

Mongoose caching that actually works.

cachegoose@4.0.1 was published on 2017-11-12. Its manifest declares 4 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All cachegoose versions · Permanent reference to 4.0.1 · Latest release

Package specifications

Version	4.0.1
License declaration	MIT
Published	2017-11-12T02:12:23.830Z
Node.js requirement	Not declared
Type declarations	Not declared
Runtime dependency count	4
Peer requirement count	1
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	index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	18
Repository stars	208
Repository forks	55

Install cachegoose 4.0.1

npm install cachegoose@4.0.1
pnpm add cachegoose@4.0.1
yarn add cachegoose@4.0.1

Runtime dependencies

cacheman ^2.0.5
cacheman-redis ^1.0.1
jsosort 0.0.0
sha1 ^1.1.0

Peer requirements

mongoose ^4.5.7

Optional dependencies

None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

@redis/bloom@6.3.0 — indirect
@redis/client@6.3.0 — indirect
@redis/json@6.3.0 — indirect
@redis/search@6.3.0 — indirect
@redis/time-series@6.3.0 — indirect
cacheman@2.2.1 — direct
cacheman-memory@1.1.0 — indirect
cacheman-redis@1.1.2 — direct
charenc@0.0.2 — indirect
crypt@0.0.2 — indirect
jsosort@0.0.0 — direct
lru-cache@4.1.5 — indirect
ms@0.7.3 — indirect
parse-redis-url@0.0.2 — indirect
pseudomap@1.0.2 — indirect
redis@6.3.0 — indirect
sha1@1.1.1 — direct
yallist@2.1.2 — indirect

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	1/10 — Found 5/30 approved changesets -- score normalized to 1
Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts	10/10 — no binaries found in the repo
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
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/cachegoose/4.0.1 — retrieved 2026-10-29T22:30:09.875Z
https://api.deps.dev/v3/projects/github.com%2Fboblauer%2Fcachegoose — retrieved 2026-10-29T19:34:48.236Z
https://api.deps.dev/v3/systems/npm/packages/cachegoose/versions/4.0.1 — retrieved 2026-10-29T22:30:10.393Z
https://api.deps.dev/v3/systems/npm/packages/cachegoose/versions/4.0.1:dependencies — retrieved 2026-10-29T22:30:10.407Z