pretty-time

npm

Is pretty-time safe to use?

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

pretty-time 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.

pretty-time Capabilities & Permissions

No system capabilities detected for pretty-time. 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 pretty-time

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

pretty-time Documentation & Source Code

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

Frequently asked questions about pretty-time safety

Weekly Downloads

1.8M

Version

1.1.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

No special capabilities detected

Is pretty-time Safe? | npm Safety Scan - brin