faker 2.1.1
Generate massive amounts of fake contextual data
faker@2.1.1 was published on 2014-11-29. Its manifest declares 0 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 faker versions · Permanent reference to 2.1.1 · Latest release
Package specifications
| Version | 2.1.1 |
|---|---|
| License declaration | Not declared |
| Published | 2014-11-29T14:31:20.140Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 0 |
| 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 | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 1572 |
| Repository forks | 751 |
Install faker 2.1.1
npm install faker@2.1.1 pnpm add faker@2.1.1 yarn add faker@2.1.1
Runtime dependencies
- None declared
Peer requirements
- None declared
Optional dependencies
- None declared
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.
Evidence and freshness
- https://registry.npmjs.org/faker/2.1.1 — retrieved 2026-10-31T20:23:24.771Z
- https://api.deps.dev/v3/projects/github.com%2FMarak%2FFaker.js — retrieved 2026-10-31T16:01:09.741Z