nu-ojtc

npm

Is nu-ojtc safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for nu-ojtc v0.1.16. Trust score: 55/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)

nu-ojtc 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.

nu-ojtc Capabilities & Permissions

What nu-ojtc 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.

/usr/ (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for nu-ojtc

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

nu-ojtc Documentation & Source Code

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

Frequently asked questions about nu-ojtc safety

Weekly Downloads

25

Version

0.1.16

License

MIT

Last Scanned

5 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Process

Spawns child processes

Is nu-ojtc Safe? | npm Safety Scan - brin