filedirname 2.0.0
Fetch the current file and directory path, no matter your environment (Deno, Node.js, Web Browsers, ESM, CJS)
filedirname@2.0.0 was published on 2020-09-03. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.
All filedirname versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2020-09-03T03:38:39.205Z |
| Node.js requirement | >=14 |
| Type declarations | Bundled declarations |
| 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 | 30.23 KiB |
| Published file count | 14 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | edition-esnext/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 16 |
| Repository forks | 3 |
Install filedirname 2.0.0
npm install filedirname@2.0.0 pnpm add filedirname@2.0.0 yarn add filedirname@2.0.0
Runtime dependencies
- get-current-line ^6.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.
- get-current-line@6.10.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/9 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 10/10 — security policy file detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 6/10 — SAST tool is not run on all commits -- score normalized to 6 |
Evidence and freshness
- https://registry.npmjs.org/filedirname/2.0.0 — retrieved 2026-10-29T21:29:02.712Z
- https://api.deps.dev/v3/projects/github.com%2Fbevry%2Ffiledirname — retrieved 2026-10-29T20:10:27.799Z
- https://api.deps.dev/v3/systems/npm/packages/filedirname/versions/2.0.0:dependencies — retrieved 2026-10-29T21:29:03.279Z
- https://api.deps.dev/v3/systems/npm/packages/filedirname/versions/2.0.0 — retrieved 2026-10-29T21:29:03.266Z