lcov-parse

npm

Is lcov-parse safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for lcov-parse v1.0.0. 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)

lcov-parse 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.

lcov-parse Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

/usr/ (r)

AGENTS.md for lcov-parse

Good instructions lead to good results. brin adds lcov-parse 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 →

lcov-parse Documentation & Source Code

For the full lcov-parse README, API documentation, and source code, visit the official package registry.

Frequently asked questions about lcov-parse safety

Weekly Downloads

606.3K

Version

1.0.0

License

BSD-3-Clause

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is lcov-parse Safe? | npm Safety Scan - brin