http-assert 1.1.0
assert with status codes
http-assert@1.1.0 was published on 2014-12-10. 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.
All http-assert versions · Permanent reference to 1.1.0 · Latest release
Package specifications
| Version | 1.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2014-12-10T17:52:06.109Z |
| 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 | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 154 |
| Repository forks | 17 |
Install http-assert 1.1.0
npm install http-assert@1.1.0 pnpm add http-assert@1.1.0 yarn add http-assert@1.1.0
Runtime dependencies
- deep-equal ~0.2.1
- http-errors ~1.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.
- deep-equal@0.2.2 — direct
- http-errors@1.2.8 — direct
- inherits@2.0.4 — indirect
- statuses@1.5.0 — 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.
| 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 | 1/10 — Found 3/29 approved changesets -- score normalized to 1 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| 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 | 4/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 9/10 — security policy file detected |
| SAST | 7/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/http-assert/1.1.0 — retrieved 2026-10-29T09:15:29.280Z
- https://api.deps.dev/v3/projects/github.com%2Fjshttp%2Fhttp-assert — retrieved 2026-10-29T05:58:10.272Z
- https://api.deps.dev/v3/systems/npm/packages/http-assert/versions/1.1.0 — retrieved 2026-10-29T09:15:29.938Z
- https://api.deps.dev/v3/systems/npm/packages/http-assert/versions/1.1.0:dependencies — retrieved 2026-10-29T09:15:29.965Z