eslint-plugin-filenames

Eslint rule for consistent filenames.

eslint-plugin-filenames@1.3.2 was published on 2018-06-13. Its manifest declares 4 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All eslint-plugin-filenames versions · Permanent reference to 1.3.2

Package specifications

Version1.3.2
License declarationMIT
Published2018-06-13T17:55:52.218Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.53 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars317
Repository forks34

Install eslint-plugin-filenames 1.3.2

npm install eslint-plugin-filenames@1.3.2
pnpm add eslint-plugin-filenames@1.3.2
yarn add eslint-plugin-filenames@1.3.2

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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-Review2/10 — Found 4/19 approved changesets -- score normalized to 2
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License0/10 — license file not detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness