update-check

npm

Is update-check safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for update-check v1.5.4. Trust score: 85/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)

update-check 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.

update-check Capabilities & Permissions

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

Filesystem Access

Reads and writes to the filesystem.

package.json (rw)

AGENTS.md for update-check

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

update-check Documentation & Source Code

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

Frequently asked questions about update-check safety

Weekly Downloads

25.3M

Version

1.5.4

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Is update-check Safe? | npm Safety Scan - brin