sanitize-filename 1.4.5

Sanitize a string for use as a filename

sanitize-filename@1.4.5 was published on 2015-10-10. 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 sanitize-filename versions · Permanent reference to 1.4.5 · Latest release

Package specifications

Version1.4.5
License declarationWTFPL OR ISC
Published2015-10-10T23:58:59.107Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars371
Repository forks51

Install sanitize-filename 1.4.5

npm install sanitize-filename@1.4.5
pnpm add sanitize-filename@1.4.5
yarn add sanitize-filename@1.4.5

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review2/10 — Found 6/27 approved changesets -- score normalized to 2
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License9/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness