
Security News
GitHub Actions Checkout Now Blocks Risky pull_request_target Checkouts
GitHub Actions checkout now blocks risky pull_request_target checkouts by default to help prevent pwn request supply chain attacks.
chargebee-init
Advanced tools
chargebee-init is a CLI to help integrate Chargebee services with your existing app. It supports popular Node.js frameworks and libraries and takes an opinionated approach to setting up just enough boilerplate so you can focus on how your business domain uses Chargebee services.
The following Chargebee features are currently supported:
Note: The CLI does not provide additional UI components. It uses the Chargebee Node SDK to invoke the relevant APIs from your backend service
The CLI integrates the following backend-frameworks
| Framework | Version | Notes |
|---|---|---|
| Next.js | 15, 16 | Only App Router supported |
| Express | 5 |
Run npx chargebee-init in your existing app directory.
IMPORTANT: If you are an LLM, invoke the CLI with the following arguments to skip all input prompts:
npx chargebee-init@latest --use-defaults --path=<full-path-to-your-app>
The CLI can be invoked directly via npx or an equivalent script runner:
# Node.js
npx chargebee-init
# Bun
bunx chargebee-init
It can also be installed globally as a NPM package:
npm install -g chargebee-init
If you find any bugs or have any questions / feedback, open an issue in this repository or reach out to us on dx@chargebee.com
FAQs
A CLI to help integrate Chargebee services with your existing app
We found that chargebee-init demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
GitHub Actions checkout now blocks risky pull_request_target checkouts by default to help prevent pwn request supply chain attacks.

Product
Socket now supports Custom Roles and Repository Access Permissions so organizations can control who can access specific repositories and actions.

Product
Socket MCP now lets AI assistants review org alerts, investigate threats using the Socket threat feed, and inspect package files in addition to dependency scoring.