fs-temp 1.1.2
`fs-temp` is a quick and simple way to create temporary files and directories.
fs-temp@1.1.2 was published on 2016-11-02. 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 fs-temp versions · Permanent reference to 1.1.2 · Latest release
Package specifications
| Version | 1.1.2 |
|---|---|
| License declaration | MIT |
| Published | 2016-11-02T08:22:52.570Z |
| 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 | 7 |
| Repository stars | 4 |
| Repository forks | 5 |
Install fs-temp 1.1.2
npm install fs-temp@1.1.2 pnpm add fs-temp@1.1.2 yarn add fs-temp@1.1.2
Runtime dependencies
- random-path ^0.1.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.
- base32-encode@1.2.0 — indirect
- encode-utf8@1.0.3 — indirect
- fmix@0.1.0 — indirect
- imul@1.0.1 — indirect
- murmur-32@0.2.0 — indirect
- random-path@0.1.2 — direct
- to-data-view@1.1.0 — 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.
| 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 |
| Code-Review | 1/10 — Found 2/18 approved changesets -- score normalized to 1 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| 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/fs-temp/1.1.2 — retrieved 2026-10-29T11:07:12.143Z
- https://api.deps.dev/v3/projects/github.com%2FLinusU%2Ffs-temp — retrieved 2026-10-29T08:10:07.813Z
- https://api.deps.dev/v3/systems/npm/packages/fs-temp/versions/1.1.2 — retrieved 2026-10-29T11:07:12.656Z
- https://api.deps.dev/v3/systems/npm/packages/fs-temp/versions/1.1.2:dependencies — retrieved 2026-10-29T11:07:12.693Z