tmp-file
Create actual and temporary file on /tmp folder
tmp-file@2.0.1 was published on 2017-01-03. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.
All tmp-file versions · Permanent reference to 2.0.1
Package specifications
| Version | 2.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2017-01-03T02:20:27.742Z |
| Node.js requirement | >=4 |
| 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 | 9 |
| Repository stars | 1 |
| Repository forks | 1 |
Install tmp-file 2.0.1
npm install tmp-file@2.0.1 pnpm add tmp-file@2.0.1 yarn add tmp-file@2.0.1
Runtime dependencies
- tmp-filepath ^2.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.
- browser-fingerprint@0.0.1 — indirect
- core-js@1.2.7 — indirect
- cuid@1.3.8 — indirect
- dom-walk@0.1.2 — indirect
- global@4.4.0 — indirect
- min-document@2.19.2 — indirect
- node-fingerprint@0.0.2 — indirect
- process@0.11.10 — indirect
- tmp-filepath@2.0.0 — 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.
| Code-Review | 0/10 — Found 0/15 approved changesets -- score normalized to 0 |
|---|---|
| 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 |
| 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 | 10/10 — security policy file detected |
Evidence and freshness
- https://registry.npmjs.org/tmp-file/2.0.1 — retrieved 2026-10-29T10:24:21.755Z
- https://api.deps.dev/v3/systems/npm/packages/tmp-file/versions/2.0.1 — retrieved 2026-10-29T10:24:22.414Z
- https://api.deps.dev/v3/systems/npm/packages/tmp-file/versions/2.0.1:dependencies — retrieved 2026-10-29T10:24:22.446Z
- https://api.deps.dev/v3/projects/github.com%2Ftunnckocore%2Ftmp-file — retrieved 2026-10-29T10:24:22.559Z