
Security News
New React Server Components Vulnerabilities: DoS and Source Code Exposure
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.
The Checkly CLI gives you a JavaScript/TypeScript-native workflow for coding, testing and deploying synthetic monitoring at scale, from your code base. We call this workflow monitoring as code (MaC).
@playwright/test support. No lock-in, just write standard *.spec.ts files.First, make sure you sign up for a free Checkly account or signup via the terminal using
npx checkly login.
Then, the easiest way to get started is to install the CLI using the following command:
npm create checkly
This command will guide you through some simple steps and set up a fully working example project for you. Should take ~1 minute.
You can also set up the CLI from scratch by running:
npm install --save-dev checkly
Official docs are over at checklyhq.com/docs/cli
Use CHECKLY_CLI_VERSION environment variable to set the latest version you want to test.
To get started with local development check CONTRIBUTING.MD
FAQs
Checkly CLI
The npm package checkly receives a total of 61,375 weekly downloads. As such, checkly popularity was classified as popular.
We found that checkly demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers 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
New DoS and source code exposure bugs in React Server Components and Next.js: what’s affected and how to update safely.

Security News
Socket CEO Feross Aboukhadijeh joins Software Engineering Daily to discuss modern software supply chain attacks and rising AI-driven security risks.

Security News
GitHub has revoked npm classic tokens for publishing; maintainers must migrate, but OpenJS warns OIDC trusted publishing still has risky gaps for critical projects.