@cyberclarence/indie-cms

npm

Is @cyberclarence/indie-cms safe to use?

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

@cyberclarence/indie-cms 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.

@cyberclarence/indie-cms Capabilities & Permissions

What @cyberclarence/indie-cms 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.

api.indiecms.ioexample.com
Protocols: https

AGENTS.md for @cyberclarence/indie-cms

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

@cyberclarence/indie-cms Documentation & Source Code

For the full @cyberclarence/indie-cms README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @cyberclarence/indie-cms safety

Weekly Downloads

16

Version

0.2.1

License

MIT

Last Scanned

2 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: api.indiecms.io, example.com

Is @cyberclarence/indie-cms Safe? | npm Safety Scan - brin