@bevry/fs-accessible 2.0.0

Check if a path is accessible

@bevry/fs-accessible@2.0.0 was published on 2023-11-17. 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 >=4.

All @bevry/fs-accessible versions · Permanent reference to 2.0.0 · Latest release

Package specifications

Version2.0.0
License declarationArtistic-2.0
Published2023-11-17T05:17:25.433Z
Node.js requirement>=4
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size40.66 KiB
Published file count18
Package typemodule
ES module entryNot declared
Default entryindex.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars1
Repository forks0

Install @bevry/fs-accessible 2.0.0

npm install @bevry/fs-accessible@2.0.0
pnpm add @bevry/fs-accessible@2.0.0
yarn add @bevry/fs-accessible@2.0.0

Runtime dependencies

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.

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-Review0/10 — Found 0/9 approved changesets -- score normalized to 0
Maintained5/10 — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
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
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness