nodefy
convert AMD modules into a node.js compatible format
nodefy@0.2.2 was published on 2013-03-05. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All nodefy versions · Permanent reference to 0.2.2
Package specifications
| Version | 0.2.2 |
|---|---|
| License declaration | MIT |
| Published | 2013-03-05T14:16:28.590Z |
| Node.js requirement | Not declared |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 11 |
| Repository stars | 65 |
| Repository forks | 10 |
Install nodefy 0.2.2
npm install nodefy@0.2.2 pnpm add nodefy@0.2.2 yarn add nodefy@0.2.2
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.
- async@0.1.22 — direct
- commander@1.1.1 — direct
- esprima@1.1.1 — direct
- glob@3.1.21 — direct
- graceful-fs@1.2.3 — indirect
- inherits@1.0.2 — indirect
- keypress@0.1.0 — indirect
- lru-cache@2.7.3 — indirect
- minimatch@0.2.14 — indirect
- mkdirp@0.3.5 — direct
- sigmund@1.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.
| Code-Review | 0/10 — Found 0/10 approved changesets -- score normalized to 0 |
|---|---|
| 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 |
| 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 |
| License | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/nodefy/0.2.2 — retrieved 2026-10-29T19:42:30.956Z
- https://api.deps.dev/v3/systems/npm/packages/nodefy/versions/0.2.2 — retrieved 2026-10-29T19:42:31.510Z
- https://api.deps.dev/v3/systems/npm/packages/nodefy/versions/0.2.2:dependencies — retrieved 2026-10-29T19:42:31.538Z
- https://api.deps.dev/v3/projects/github.com%2Fmillermedeiros%2Fnodefy — retrieved 2026-10-29T19:42:31.677Z