espower 0.4.0
Power Assert feature instrumentor based on the Mozilla JavaScript AST
espower@0.4.0 was published on 2014-03-27. Its manifest declares 1 runtime dependency 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 espower versions · Permanent reference to 0.4.0 · Latest release
Package specifications
| Version | 0.4.0 |
|---|---|
| License declaration | Not declared |
| Published | 2014-03-27T09:16:56.646Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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/espower |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 59 |
| Repository forks | 6 |
Install espower 0.4.0
npm install espower@0.4.0 pnpm add espower@0.4.0 yarn add espower@0.4.0
Runtime dependencies
- estraverse ~1.5.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.
- estraverse@1.5.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.
| 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 0/13 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| 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/espower/0.4.0 — retrieved 2026-10-29T17:45:32.710Z
- https://api.deps.dev/v3/projects/github.com%2Fpower-assert-js%2Fespower — retrieved 2026-10-29T16:40:36.138Z
- https://api.deps.dev/v3/systems/npm/packages/espower/versions/0.4.0 — retrieved 2026-10-29T17:45:33.342Z
- https://api.deps.dev/v3/systems/npm/packages/espower/versions/0.4.0:dependencies — retrieved 2026-10-29T17:45:33.532Z