eslint-config-bevry

Intelligent, self-configuring ESLint configuration that automatically analyzes your project structure, dependencies, and metadata to apply optimal linting rules for JavaScript, TypeScript, React, Node.js, and more.

eslint-config-bevry@6.1.6 was published on 2025-08-12. Its manifest declares 14 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=20.

All eslint-config-bevry versions · Permanent reference to 6.1.6

Package specifications

Version6.1.6
License declarationArtistic-2.0
Published2025-08-12T19:04:11.762Z
Node.js requirement>=20
Type declarationsNot declared
Runtime dependency count14
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size100.00 KiB
Published file count9
Package typemodule
ES module entryNot declared
Default entrysource/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies230
Repository stars4
Repository forks0

Install eslint-config-bevry 6.1.6

npm install eslint-config-bevry@6.1.6
pnpm add eslint-config-bevry@6.1.6
yarn add eslint-config-bevry@6.1.6

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 0/11 approved changesets -- score normalized to 0
Security-Policy10/10 — security policy file detected
Maintained5/10 — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST9/10 — SAST tool is not run on all commits -- score normalized to 9

Evidence and freshness