file-entry-cache

npm

Is file-entry-cache safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for file-entry-cache v11.1.2. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

file-entry-cache Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

file-entry-cache Capabilities & Permissions

What file-entry-cache can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

AGENTS.md for file-entry-cache

Good instructions lead to good results. brin adds file-entry-cache documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

file-entry-cache Documentation & Source Code

For the full file-entry-cache README, API documentation, and source code, visit the official package registry.

Frequently asked questions about file-entry-cache safety

Weekly Downloads

73.2M

Version

11.1.2

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is file-entry-cache Safe? | npm Safety Scan - brin