brin
brin

@iold/old-core

npm

Is @iold/old-core safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @iold/old-core v1.0.8. 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)

@iold/old-core 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.

@iold/old-core Capabilities & Permissions

What @iold/old-core can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Writes to the filesystem.

package.json (w)package.json (w)node_modules (w)package.json (w)package.json (w)

Process Spawning

This package can spawn child processes.

git

AGENTS.md for @iold/old-core

Good instructions lead to good results. brin adds @iold/old-core 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 →

@iold/old-core Documentation & Source Code

For the full @iold/old-core README, API documentation, and source code, visit the official package registry.

View on npm

Frequently asked questions about @iold/old-core safety

Weekly Downloads

22

Version

1.0.8

License

MIT

Last Scanned

1 day ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files

Process

Spawns child processes

Is @iold/old-core Safe? | npm Safety Scan - brin