unassertify 2.0.4
Browserify transform to encourage reliable programming by writing assertions in production code, and compiling them away from release
unassertify@2.0.4 was published on 2016-12-28. Its manifest declares 6 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 unassertify versions · Permanent reference to 2.0.4 · Latest release
Package specifications
| Version | 2.0.4 |
|---|---|
| License declaration | MIT |
| Published | 2016-12-28T02:03:21.025Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| 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 | 54 |
| Repository stars | 78 |
| Repository forks | 5 |
Install unassertify 2.0.4
npm install unassertify@2.0.4 pnpm add unassertify@2.0.4 yarn add unassertify@2.0.4
Runtime dependencies
- acorn ^4.0.0
- convert-source-map ^1.1.1
- escodegen ^1.6.1
- multi-stage-sourcemap ^0.2.1
- through ^2.3.7
- unassert ^1.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.
- acorn@4.0.13 — direct
- acorn@7.4.1 — indirect
- amdefine@1.0.1 — indirect
- async-function@1.0.0 — indirect
- async-generator-function@1.0.0 — indirect
- call-bind@1.0.9 — indirect
- call-bind-apply-helpers@1.0.2 — indirect
- call-bound@1.0.4 — indirect
- call-matcher@2.0.0 — indirect
- convert-source-map@1.9.0 — direct
- deep-equal@1.1.2 — indirect
- deep-is@0.1.4 — indirect
- define-data-property@1.1.4 — indirect
- define-properties@1.2.1 — indirect
- 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
- escodegen@1.14.3 — direct
- esprima@4.0.1 — indirect
- espurify@2.1.1 — indirect
- estraverse@4.3.0 — indirect
- esutils@2.0.3 — indirect
- fast-levenshtein@2.0.6 — indirect
- function-bind@1.1.2 — indirect
- functions-have-names@1.2.3 — indirect
- generator-function@2.0.1 — indirect
- get-intrinsic@1.3.1 — indirect
- get-proto@1.0.1 — indirect
- gopd@1.2.0 — indirect
- has-property-descriptors@1.0.2 — indirect
- has-symbols@1.1.0 — indirect
- has-tostringtag@1.0.2 — indirect
- hasown@2.0.4 — indirect
- is-arguments@1.2.0 — indirect
- is-date-object@1.1.0 — indirect
- is-regex@1.2.1 — indirect
- levn@0.3.0 — indirect
- math-intrinsics@1.1.0 — indirect
- multi-stage-sourcemap@0.2.1 — direct
- object-assign@4.1.1 — indirect
- object-is@1.1.6 — indirect
- object-keys@1.1.1 — indirect
- optionator@0.8.3 — indirect
- prelude-ls@1.1.2 — indirect
- regexp.prototype.flags@1.5.4 — indirect
- set-function-length@1.2.2 — indirect
- set-function-name@2.0.2 — indirect
- source-map@0.1.43 — indirect
- source-map@0.6.1 — indirect
- through@2.3.8 — direct
- type-check@0.3.2 — indirect
- unassert@1.6.0 — direct
- word-wrap@1.2.5 — 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.
| Code-Review | 0/10 — Found 1/18 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 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/unassertify/2.0.4 — retrieved 2026-10-29T12:30:43.674Z
- https://api.deps.dev/v3/projects/github.com%2Funassert-js%2Funassertify — retrieved 2026-10-29T07:08:58.673Z
- https://api.deps.dev/v3/systems/npm/packages/unassertify/versions/2.0.4 — retrieved 2026-10-29T12:30:44.235Z
- https://api.deps.dev/v3/systems/npm/packages/unassertify/versions/2.0.4:dependencies — retrieved 2026-10-29T12:30:44.248Z