chargebee

PyPI

Is chargebee safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for chargebee v3.18.2. Trust score: 60/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)

chargebee 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.

chargebee Capabilities & Permissions

What chargebee 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.

apidocs.chargebee.comtest_site.ingest.chargebee.com
Protocols: https

Filesystem Access

Reads from the filesystem.

.env (r).env (r).env (r).env (r).env (r).env (r).env (r).env (r)+55 more

AGENTS.md for chargebee

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

chargebee Documentation & Source Code

For the full chargebee README, API documentation, and source code, visit the official package registry.

Frequently asked questions about chargebee safety

Weekly Downloads

175.1K

Version

3.18.2

Other Versions

Last Scanned

2 days ago

Trust Score

60/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: apidocs.chargebee.com, test_site.ingest.chargebee.com

Filesystem

Reads files