question-store 0.1.8
Ask questions, persist the answers. Basic support for i18n and storing answers based on current working directory.
question-store@0.1.8 was published on 2015-11-27. Its manifest declares 10 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All question-store versions · Permanent reference to 0.1.8 · Latest release
Package specifications
| Version | 0.1.8 |
|---|---|
| License declaration | MIT |
| Published | 2015-11-27T10:24:57.468Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 10 |
| 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 | 65 |
| Repository stars | 11 |
| Repository forks | 2 |
Install question-store 0.1.8
npm install question-store@0.1.8 pnpm add question-store@0.1.8 yarn add question-store@0.1.8
Runtime dependencies
- answer-store ^0.1.2
- async ^1.5.0
- define-property ^0.2.5
- extend-shallow ^2.0.1
- get-value ^2.0.0
- inquirer2 github:jonschlinkert/inquirer2
- isobject ^2.0.0
- lazy-cache ^0.2.4
- resolve-dir ^0.1.0
- set-value ^0.3.1
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.
- answer-store@0.1.3 — direct
- arr-flatten@1.1.0 — indirect
- async@1.5.2 — direct
- async-function@1.0.0 — indirect
- async-generator-function@1.0.0 — indirect
- balanced-match@1.0.2 — indirect
- brace-expansion@1.1.21 — indirect
- call-bind-apply-helpers@1.0.2 — indirect
- call-bound@1.0.4 — indirect
- concat-map@0.0.1 — indirect
- define-property@0.2.5 — direct
- dunder-proto@1.0.1 — indirect
- es-define-property@1.0.1 — indirect
- es-errors@1.3.0 — indirect
- es-object-atoms@1.1.2 — indirect
- expand-tilde@1.2.2 — indirect
- extend-shallow@2.0.1 — direct
- fs.realpath@1.0.0 — indirect
- function-bind@1.1.2 — indirect
- generator-function@2.0.1 — indirect
- get-intrinsic@1.3.1 — indirect
- get-proto@1.0.1 — indirect
- get-value@2.0.6 — direct
- glob@7.2.3 — indirect
- global-modules@0.2.3 — indirect
- global-prefix@0.1.5 — indirect
- gopd@1.2.0 — indirect
- has-symbols@1.1.0 — indirect
- has-tostringtag@1.0.2 — indirect
- has-value@0.3.1 — indirect
- has-values@0.1.4 — indirect
- hasown@2.0.4 — indirect
- homedir-polyfill@1.0.3 — indirect
- inflight@1.0.6 — indirect
- inherits@2.0.4 — indirect
- ini@1.3.8 — indirect
- is-accessor-descriptor@1.0.2 — indirect
- is-arguments@1.2.0 — indirect
- is-data-descriptor@1.0.1 — indirect
- is-descriptor@0.1.8 — indirect
- is-extendable@0.1.1 — indirect
- is-windows@0.2.0 — indirect
- isarray@1.0.0 — indirect
- isexe@2.0.0 — indirect
- isobject@2.1.0 — direct
- isobject@3.0.1 — indirect
- lazy-cache@0.2.7 — direct
- lazy-cache@1.0.4 — indirect
- math-intrinsics@1.1.0 — indirect
- minimatch@3.1.5 — indirect
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — indirect
- once@1.4.0 — indirect
- os-homedir@1.0.2 — indirect
- parse-passwd@1.0.0 — indirect
- path-is-absolute@1.0.1 — indirect
- resolve-dir@0.1.1 — direct
- rimraf@2.7.1 — indirect
- set-value@0.3.3 — direct
- to-object-path@0.2.0 — indirect
- unset-value@0.1.2 — indirect
- which@1.3.1 — indirect
- wrappy@1.0.2 — indirect
- write@0.2.1 — indirect
- write-json@0.2.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.
| SAST | 0/10 — no SAST tool detected |
|---|---|
| Code-Review | 0/10 — Found 0/30 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 |
Evidence and freshness
- https://registry.npmjs.org/question-store/0.1.8 — retrieved 2026-10-30T01:56:37.919Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fquestion-store — retrieved 2026-10-30T01:02:48.995Z
- https://api.deps.dev/v3/systems/npm/packages/question-store/versions/0.1.8 — retrieved 2026-10-30T01:56:38.403Z
- https://api.deps.dev/v3/systems/npm/packages/question-store/versions/0.1.8:dependencies — retrieved 2026-10-30T01:56:38.465Z