@ryancavanaugh/jsnlog

npm

Is @ryancavanaugh/jsnlog safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @ryancavanaugh/jsnlog v2.11.13-alpha. 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)

@ryancavanaugh/jsnlog 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.

@ryancavanaugh/jsnlog Capabilities & Permissions

What @ryancavanaugh/jsnlog 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.

github.comjsnlog.com
Protocols: http, https

AGENTS.md for @ryancavanaugh/jsnlog

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

@ryancavanaugh/jsnlog Documentation & Source Code

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

Frequently asked questions about @ryancavanaugh/jsnlog safety

Weekly Downloads

12

Version

2.11.13-alpha

License

MIT

Last Scanned

1 day ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, jsnlog.com

Is @ryancavanaugh/jsnlog Safe? | npm Safety Scan - brin