@spankdev/spankbank

npm

Is @spankdev/spankbank safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @spankdev/spankbank v0.1.0-rc2. 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)

@spankdev/spankbank 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.

@spankdev/spankbank Capabilities & Permissions

What @spankdev/spankbank 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.

/tmp/ (rw)/usr/ (rw)

AGENTS.md for @spankdev/spankbank

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

@spankdev/spankbank Documentation & Source Code

For the full @spankdev/spankbank README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @spankdev/spankbank safety

Weekly Downloads

18

Version

0.1.0-rc2

Last Scanned

15 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Is @spankdev/spankbank Safe? | npm Safety Scan - brin