pnpm-file-reporter
A file reporter for pnpm
pnpm-file-reporter@0.1.0 was published on 2018-03-07. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=4.
All pnpm-file-reporter versions · Permanent reference to 0.1.0
Package specifications
| Version | 0.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-03-07T21:12:06.683Z |
| Node.js requirement | >=4 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 6.99 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 2 |
| Repository forks | 0 |
Install pnpm-file-reporter 0.1.0
npm install pnpm-file-reporter@0.1.0 pnpm add pnpm-file-reporter@0.1.0 yarn add pnpm-file-reporter@0.1.0
Runtime dependencies
- @types/graceful-fs ^4.1.2
- @types/node ^9.4.6
- graceful-fs ^4.1.11
- json2yaml ^1.1.0
- path-exists ^3.0.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.
- @types/graceful-fs@4.1.9 — direct
- @types/node@9.6.61 — direct
- graceful-fs@4.2.11 — direct
- json2yaml@1.1.0 — direct
- path-exists@3.0.0 — direct
- remedial@1.0.8 — 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.
| Maintained | 0/10 — project is archived |
|---|---|
| Code-Review | 0/10 — Found 0/18 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 |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/pnpm-file-reporter/0.1.0 — retrieved 2026-10-31T21:08:22.208Z
- https://api.deps.dev/v3/systems/npm/packages/pnpm-file-reporter/versions/0.1.0 — retrieved 2026-10-31T21:08:22.659Z
- https://api.deps.dev/v3/systems/npm/packages/pnpm-file-reporter/versions/0.1.0:dependencies — retrieved 2026-10-31T21:08:22.681Z
- https://api.deps.dev/v3/projects/github.com%2Fpnpm%2Fpnpm-file-reporter — retrieved 2026-10-31T21:08:23.218Z