items 1.0.2
Bare minimum async methods
items@1.0.2 was published on 2014-09-05. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.30.
Deprecated: This module has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version of hapi to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
All items versions · Permanent reference to 1.0.2 · Latest release
Package specifications
| Version | 1.0.2 |
|---|---|
| License declaration | Not declared |
| Published | 2014-09-05T18:56:38.685Z |
| Node.js requirement | >=0.10.30 |
| Type declarations | Not declared |
| Runtime dependency count | 0 |
| 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 |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 0 |
| Repository stars | 30 |
| Repository forks | 16 |
Install items 1.0.2
npm install items@1.0.2 pnpm add items@1.0.2 yarn add items@1.0.2
Runtime dependencies
- None declared
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.
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 2/25 approved changesets -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/items/1.0.2 — retrieved 2026-10-29T13:36:55.397Z
- https://api.deps.dev/v3/projects/github.com%2Fhapijs%2Fitems — retrieved 2026-10-29T11:05:30.154Z
- https://api.deps.dev/v3/systems/npm/packages/items/versions/1.0.2 — retrieved 2026-10-29T13:36:55.959Z
- https://api.deps.dev/v3/systems/npm/packages/items/versions/1.0.2:dependencies — retrieved 2026-10-29T13:36:55.970Z