i-apify 0.2.0
A api solution for `node runtime` and `web browser` based Fetch api!
i-apify@0.2.0 was published on 2017-12-04. Its manifest declares 7 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 i-apify versions · Permanent reference to 0.2.0 · Latest release
Package specifications
| Version | 0.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2017-12-04T04:07:08.600Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 7 |
| 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 | dist/index.min.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 15 |
| Repository stars | 3 |
| Repository forks | 0 |
Install i-apify 0.2.0
npm install i-apify@0.2.0 pnpm add i-apify@0.2.0 yarn add i-apify@0.2.0
Runtime dependencies
- deep-assign ^2.0.0
- detect-node ^2.0.3
- es6-promise ^4.1.1
- node-fetch ^1.7.3
- query-string ^5.0.0
- underscore ^1.8.3
- whatwg-fetch ^2.0.3
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.
- decode-uri-component@0.2.2 — indirect
- deep-assign@2.0.0 — direct
- detect-node@2.1.0 — direct
- encoding@0.1.14 — indirect
- es6-promise@4.2.8 — direct
- iconv-lite@0.7.3 — indirect
- is-obj@1.0.1 — indirect
- is-stream@1.1.0 — indirect
- node-fetch@1.7.3 — direct
- object-assign@4.1.1 — indirect
- query-string@5.1.1 — direct
- safer-buffer@2.1.2 — indirect
- strict-uri-encode@1.1.0 — indirect
- underscore@1.13.8 — direct
- whatwg-fetch@2.0.4 — 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/21 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/i-apify/0.2.0 — retrieved 2026-10-29T11:07:40.536Z
- https://api.deps.dev/v3/projects/github.com%2FNeverland%2Fapify — retrieved 2026-10-29T09:02:46.493Z
- https://api.deps.dev/v3/systems/npm/packages/i-apify/versions/0.2.0 — retrieved 2026-10-29T11:07:41.043Z
- https://api.deps.dev/v3/systems/npm/packages/i-apify/versions/0.2.0:dependencies — retrieved 2026-10-29T11:07:41.071Z