supersoaker

npm

Is supersoaker safe to use?

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

supersoaker 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.

supersoaker Capabilities & Permissions

What supersoaker can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

NPM_EMAILNPM_PASSWORDNPM_REGISTRYNPM_USER

AGENTS.md for supersoaker

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

supersoaker Documentation & Source Code

For the full supersoaker README, API documentation, and source code, visit the official package registry.

Frequently asked questions about supersoaker safety

Weekly Downloads

42

Version

1.0.1

License

MIT

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: NPM_EMAIL, NPM_PASSWORD, NPM_REGISTRY...

Is supersoaker Safe? | npm Safety Scan - brin