@0xproject/utils 0.1.3
0x TS utils
@0xproject/utils@0.1.3 was published on 2018-01-11. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @0xproject/utils versions · Permanent reference to 0.1.3 · Latest release
Package specifications
| Version | 0.1.3 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2018-01-11T12:05:53.885Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| 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 | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 1408 |
| Repository forks | 458 |
Install @0xproject/utils 0.1.3
npm install @0xproject/utils@0.1.3 pnpm add @0xproject/utils@0.1.3 yarn add @0xproject/utils@0.1.3
Runtime dependencies
- bignumber.js ~4.1.0
- js-sha3 ^0.7.0
- lodash ^4.17.4
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.
- bignumber.js@4.1.0 — direct
- js-sha3@0.7.0 — direct
- lodash@4.18.1 — 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 | 5/10 — Found 4/8 approved changesets -- score normalized to 5 |
|---|---|
| Maintained | 0/10 — project is archived |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 0/10 — security policy file not detected |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
Evidence and freshness
- https://registry.npmjs.org/%400xproject%2Futils/0.1.3 — retrieved 2026-10-30T17:41:17.201Z
- https://api.deps.dev/v3/projects/github.com%2F0xProject%2F0x-monorepo — retrieved 2026-10-30T14:35:43.062Z
- https://api.deps.dev/v3/systems/npm/packages/%400xproject%2Futils/versions/0.1.3 — retrieved 2026-10-30T17:41:17.607Z
- https://api.deps.dev/v3/systems/npm/packages/%400xproject%2Futils/versions/0.1.3:dependencies — retrieved 2026-10-30T17:41:17.612Z