node-haste 2.0.0-alpha1
Node Haste is a dependency management system for static resources for node.js
node-haste@2.0.0-alpha1 was published on 2015-11-14. Its manifest declares 3 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 node-haste versions · Permanent reference to 2.0.0-alpha1 · Latest release
Package specifications
| Version | 2.0.0-alpha1 |
|---|---|
| License declaration | BSD-3-Clause |
| Published | 2015-11-14T00:51:11.386Z |
| Node.js requirement | Not declared |
| 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 | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 221 |
| Repository forks | 68 |
Install node-haste 2.0.0-alpha1
npm install node-haste@2.0.0-alpha1 pnpm add node-haste@2.0.0-alpha1 yarn add node-haste@2.0.0-alpha1
Runtime dependencies
- debug ^2.2.0
- promise ^7.0.4
- absolute-path ^0.0.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.
- absolute-path@0.0.0 — direct
- asap@2.0.6 — indirect
- debug@2.6.9 — direct
- ms@2.0.0 — indirect
- promise@7.3.1 — 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 |
|---|---|
| SAST | 0/10 — no SAST tool detected |
| Maintained | 0/10 — project is archived |
| Code-Review | 0/10 — Found 0/1 approved changesets -- 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 |
| License | 0/10 — license file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
Evidence and freshness
- https://registry.npmjs.org/node-haste/2.0.0-alpha1 — retrieved 2026-10-31T19:38:14.442Z
- https://api.deps.dev/v3/projects/github.com%2Ffacebook%2Fnode-haste — retrieved 2026-10-31T19:34:18.675Z
- https://api.deps.dev/v3/systems/npm/packages/node-haste/versions/2.0.0-alpha1 — retrieved 2026-10-31T19:38:14.817Z
- https://api.deps.dev/v3/systems/npm/packages/node-haste/versions/2.0.0-alpha1:dependencies — retrieved 2026-10-31T19:38:14.843Z