are-we-there-yet 1.0.5
Keep track of the overall completion of many dispirate processes
are-we-there-yet@1.0.5 was published on 2015-12-06. Its manifest declares 2 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.
Deprecated: This package is no longer supported.
All are-we-there-yet versions · Permanent reference to 1.0.5 · Latest release
Package specifications
| Version | 1.0.5 |
|---|---|
| License declaration | ISC |
| Published | 2015-12-06T00:50:14.344Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| 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 | 9 |
| Repository stars | 183 |
| Repository forks | 23 |
Install are-we-there-yet 1.0.5
npm install are-we-there-yet@1.0.5 pnpm add are-we-there-yet@1.0.5 yarn add are-we-there-yet@1.0.5
Runtime dependencies
- delegates ^0.1.0
- readable-stream ^2.0.0 || ^1.1.13
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.
- core-util-is@1.0.3 — indirect
- delegates@0.1.0 — direct
- inherits@2.0.4 — indirect
- isarray@1.0.0 — indirect
- process-nextick-args@2.0.1 — indirect
- readable-stream@2.3.8 — direct
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- util-deprecate@1.0.2 — 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 — project is archived |
|---|---|
| Code-Review | 10/10 — all changesets reviewed |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 10/10 — security policy file detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| SAST | 7/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/are-we-there-yet/1.0.5 — retrieved 2026-10-29T09:45:15.540Z
- https://api.deps.dev/v3/projects/github.com%2Fnpm%2Fare-we-there-yet — retrieved 2026-10-29T07:11:10.541Z
- https://api.deps.dev/v3/systems/npm/packages/are-we-there-yet/versions/1.0.5 — retrieved 2026-10-29T09:45:16.242Z
- https://api.deps.dev/v3/systems/npm/packages/are-we-there-yet/versions/1.0.5:dependencies — retrieved 2026-10-29T09:45:16.269Z