q-i 1.1.0
Node.js objects inspector with color highlighting
q-i@1.1.0 was published on 2017-09-20. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All q-i versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-09-20T12:51:20.336Z |
| Node.js requirement | >=6 |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 63 |
| Repository forks | 9 |
Install q-i 1.1.0
npm install q-i@1.1.0 pnpm add q-i@1.1.0 yarn add q-i@1.1.0
Runtime dependencies
- ansi-styles ^3.2.0
- lodash ^4.17.4
- stringify-object ^3.2.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.
- ansi-styles@3.2.1 — direct
- color-convert@1.9.3 — indirect
- color-name@1.1.3 — indirect
- get-own-enumerable-property-symbols@3.0.2 — indirect
- is-obj@1.0.1 — indirect
- is-regexp@1.0.0 — indirect
- lodash@4.18.1 — direct
- stringify-object@3.3.0 — 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.
| Code-Review | 0/10 — Found 2/22 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 |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/q-i/1.1.0 — retrieved 2026-10-30T05:01:11.179Z
- https://api.deps.dev/v3/projects/github.com%2Fsapegin%2Fq-i — retrieved 2026-10-30T04:21:31.741Z
- https://api.deps.dev/v3/systems/npm/packages/q-i/versions/1.1.0 — retrieved 2026-10-30T05:01:11.698Z
- https://api.deps.dev/v3/systems/npm/packages/q-i/versions/1.1.0:dependencies — retrieved 2026-10-30T05:01:11.718Z