@jsemajtacka/iris-content-blocks

npm

Is @jsemajtacka/iris-content-blocks safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @jsemajtacka/iris-content-blocks v0.0.6. 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)

@jsemajtacka/iris-content-blocks 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.

@jsemajtacka/iris-content-blocks Capabilities & Permissions

What @jsemajtacka/iris-content-blocks 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.

AGENTS.md for @jsemajtacka/iris-content-blocks

Good instructions lead to good results. brin adds @jsemajtacka/iris-content-blocks 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 →

@jsemajtacka/iris-content-blocks Documentation & Source Code

For the full @jsemajtacka/iris-content-blocks README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @jsemajtacka/iris-content-blocks safety

Weekly Downloads

6

Version

0.0.6

License

MIT

Last Scanned

8 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Makes network requests

Is @jsemajtacka/iris-content-blocks Safe? | npm Safety Scan - brin