working-times

npm

Is working-times safe to use?

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

working-times Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

1

Install Scripts Detected

prepare

This package runs scripts during installation. Review these scripts before installing.

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.

working-times Capabilities & Permissions

No system capabilities detected for working-times. 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 working-times

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

working-times Documentation & Source Code

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

Frequently asked questions about working-times safety

Weekly Downloads

24

Version

1.1.12

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Install Scripts

This package has install scripts that run automatically:

prepare

Capabilities

No special capabilities detected

Is working-times Safe? | npm Safety Scan - brin