replace-method 0.0.0
JavaScript post-processing step to replace specific function/method calls with other bits of JavaScript
replace-method@0.0.0 was published on 2014-02-05. 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 replace-method versions · Permanent reference to 0.0.0 · Latest release
Package specifications
| Version | 0.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2014-02-05T04:02:03.794Z |
| 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 | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 1 |
| Repository forks | 1 |
Install replace-method 0.0.0
npm install replace-method@0.0.0 pnpm add replace-method@0.0.0 yarn add replace-method@0.0.0
Runtime dependencies
- recast ~0.5.7
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.
- amdefine@1.0.1 — indirect
- ast-types@0.3.38 — indirect
- cls@0.1.5 — indirect
- private@0.1.8 — indirect
- recast@0.5.27 — direct
- source-map@0.1.32 — 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 0/1 approved changesets -- score normalized to 0 |
|---|---|
| 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 |
| SAST | 0/10 — no SAST tool detected |
| 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 |
Evidence and freshness
- https://registry.npmjs.org/replace-method/0.0.0 — retrieved 2026-10-29T13:02:55.493Z
- https://api.deps.dev/v3/systems/npm/packages/replace-method/versions/0.0.0:dependencies — retrieved 2026-10-29T12:05:30.696Z
- https://api.deps.dev/v3/systems/npm/packages/replace-method/versions/0.0.0 — retrieved 2026-10-29T12:05:30.669Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fhughsk%2Freplace-method — retrieved 2026-10-29T12:05:30.822Z