ocpp-rpc

npm

Is ocpp-rpc safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for ocpp-rpc v2.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)

ocpp-rpc 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.

ocpp-rpc Capabilities & Permissions

What ocpp-rpc 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.

0.0.0.0developer.mozilla.orgjson-schema.org
Protocols: http, https, websocket

AGENTS.md for ocpp-rpc

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

ocpp-rpc Documentation & Source Code

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

Frequently asked questions about ocpp-rpc safety

Weekly Downloads

1.6K

Version

2.2.1

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: 0.0.0.0, developer.mozilla.org, json-schema.org

Is ocpp-rpc Safe? | npm Safety Scan - brin