requireg 0.2.2
Require and resolve global modules like a boss
requireg@0.2.2 was published on 2019-05-24. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 4.0.0.
All requireg versions · Permanent reference to 0.2.2 · Latest release
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | Not declared |
| Published | 2019-05-24T08:09:42.873Z |
| Node.js requirement | >= 4.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 52.32 KiB |
| Published file count | 11 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/requireg |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 45 |
| Repository forks | 13 |
Install requireg 0.2.2
npm install requireg@0.2.2 pnpm add requireg@0.2.2 yarn add requireg@0.2.2
Runtime dependencies
- nested-error-stacks ~2.0.1
- rc ~1.2.7
- resolve ~1.7.1
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.
- deep-extend@0.6.0 — indirect
- ini@1.3.8 — indirect
- minimist@1.2.8 — indirect
- nested-error-stacks@2.0.1 — direct
- path-parse@1.0.7 — indirect
- rc@1.2.8 — direct
- resolve@1.7.1 — direct
- strip-json-comments@2.0.1 — 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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Code-Review | 3/10 — Found 6/19 approved changesets -- score normalized to 3 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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/requireg/0.2.2 — retrieved 2026-10-29T12:27:00.248Z
- https://api.deps.dev/v3/systems/npm/packages/requireg/versions/0.2.2:dependencies — retrieved 2026-10-29T09:50:35.804Z
- https://api.deps.dev/v3/systems/npm/packages/requireg/versions/0.2.2 — retrieved 2026-10-29T09:50:35.749Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fh2non%2Frequireg — retrieved 2026-10-29T09:50:35.923Z