last-run

npm

Is last-run safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for last-run v2.0.0. Trust score: 75/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)

last-run 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.

last-run Capabilities & Permissions

No system capabilities detected for last-run. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.

AGENTS.md for last-run

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

last-run Documentation & Source Code

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

Frequently asked questions about last-run safety

Weekly Downloads

1.6M

Version

2.0.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is last-run Safe? | npm Safety Scan - brin