ether-pudding 2.0.9
Pudding - a (more) delightful Ethereum contract abstraction
ether-pudding@2.0.9 was published on 2016-05-11. 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 ether-pudding versions · Permanent reference to 2.0.9 · Latest release
Package specifications
| Version | 2.0.9 |
|---|---|
| License declaration | MIT License. Copyright Consensys LLC, and authors. All rights reserved. |
| Published | 2016-05-11T16:17:19.472Z |
| 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 | ./index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 254 |
| Repository forks | 53 |
Install ether-pudding 2.0.9
npm install ether-pudding@2.0.9 pnpm add ether-pudding@2.0.9 yarn add ether-pudding@2.0.9
Runtime dependencies
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.
- balanced-match@1.0.2 — indirect
- bluebird@3.7.2 — direct
- brace-expansion@1.1.21 — indirect
- concat-map@0.0.1 — indirect
- minimatch@3.1.5 — indirect
- node-dir@0.1.17 — 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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Maintained | 0/10 — project is archived |
| Code-Review | 1/10 — Found 2/20 approved changesets -- score normalized to 1 |
| 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 |
| Security-Policy | 0/10 — security policy file not 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/ether-pudding/2.0.9 — retrieved 2026-10-30T19:38:48.894Z
- https://api.deps.dev/v3/systems/npm/packages/ether-pudding/versions/2.0.9 — retrieved 2026-10-30T19:38:49.355Z
- https://api.deps.dev/v3/systems/npm/packages/ether-pudding/versions/2.0.9:dependencies — retrieved 2026-10-30T19:38:49.377Z
- https://api.deps.dev/v3/projects/github.com%2Fconsensys%2Fether-pudding — retrieved 2026-10-30T19:38:49.901Z