namify 0.1.2
Convert a npm package name into a safe-to-use variable name. Use as a mixin in Yeoman generators.
namify@0.1.2 was published on 2014-05-11. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.
All namify versions · Permanent reference to 0.1.2 · Latest release
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-05-11T10:40:04.825Z |
| Node.js requirement | >=0.8 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | 1 |
| Repository stars | 4 |
| Repository forks | 0 |
Install namify 0.1.2
npm install namify@0.1.2 pnpm add namify@0.1.2 yarn add namify@0.1.2
Runtime dependencies
- reserved ^0.1.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.
- reserved@0.1.2 — 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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 0/10 — Found 0/5 approved changesets -- 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 |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/namify/0.1.2 — retrieved 2026-10-29T23:19:31.214Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fnamify — retrieved 2026-10-29T22:51:32.926Z
- https://api.deps.dev/v3/systems/npm/packages/namify/versions/0.1.2 — retrieved 2026-10-29T23:19:31.735Z
- https://api.deps.dev/v3/systems/npm/packages/namify/versions/0.1.2:dependencies — retrieved 2026-10-29T23:19:31.747Z