brin
brin

github-commander

npm

Is github-commander safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for github-commander v0.12.0. 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)

github-commander 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.

github-commander Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

/usr/ (r)/usr/ (r)/usr/ (r)/usr/ (r)/usr/ (r)/usr/ (r)/usr/ (r)/usr/ (r)+3 more

Process Spawning

This package can spawn child processes.

AGENTS.md for github-commander

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

github-commander Documentation & Source Code

For the full github-commander README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about github-commander safety

Weekly Downloads

16

Version

0.12.0

License

MIT

Last Scanned

3 hours ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes