use-plugin 2.4.0
Generic plugin loader functionality for Node.js frameworks.
use-plugin@2.4.0 was published on 2018-10-07. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.
All use-plugin versions · Permanent reference to 2.4.0 · Latest release
Package specifications
| Version | 2.4.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-10-07T21:38:39.499Z |
| Node.js requirement | >=4 |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 22.82 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | use.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 10 |
| Repository stars | 12 |
| Repository forks | 4 |
Install use-plugin 2.4.0
npm install use-plugin@2.4.0 pnpm add use-plugin@2.4.0 yarn add use-plugin@2.4.0
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.
- eraro@1.0.0 — direct
- hoek@4.2.1 — indirect
- isemail@3.2.0 — indirect
- joi@12.0.0 — indirect
- lodash@4.17.23 — indirect
- nid@0.3.2 — direct
- norma@0.4.1 — direct
- optioner@3.0.0 — direct
- punycode@2.3.1 — indirect
- topo@2.1.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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| License | 10/10 — license file detected |
Evidence and freshness
- https://registry.npmjs.org/use-plugin/2.4.0 — retrieved 2026-10-29T22:36:31.457Z
- https://api.deps.dev/v3/projects/github.com%2Frjrodger%2Fuse-plugin — retrieved 2026-10-29T22:11:46.010Z
- https://api.deps.dev/v3/systems/npm/packages/use-plugin/versions/2.4.0 — retrieved 2026-10-29T22:36:31.984Z
- https://api.deps.dev/v3/systems/npm/packages/use-plugin/versions/2.4.0:dependencies — retrieved 2026-10-29T22:36:31.985Z