@jimbly/howler

npm

Is @jimbly/howler safe to use?

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

@jimbly/howler 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.

@jimbly/howler Capabilities & Permissions

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

Network Access

This package makes network requests.

dev.w3.orgpaulbakaus.comstackoverflow.com
Protocols: http

Process Spawning

This package can spawn child processes.

AGENTS.md for @jimbly/howler

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

@jimbly/howler Documentation & Source Code

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

Frequently asked questions about @jimbly/howler safety

Weekly Downloads

154

Version

0.1.9

License

MIT

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: dev.w3.org, paulbakaus.com, stackoverflow.com

Process

Spawns child processes

Is @jimbly/howler Safe? | npm Safety Scan - brin