inngest
npmIs inngest safe to use?
The latest brin safety scan flagged inngest v3.50.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
inngest Has Warnings
Warnings detected due to potential concerns
0
0
0
Risk Indicators
- •Can spawn child processes
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add inngest to automatically apply these checks before installation.
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.
inngest Capabilities & Permissions
What inngest 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.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for inngest
Good instructions lead to good results. brin adds inngest documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
inngest Documentation & Source Code
For the full inngest README, API documentation, and source code, visit the official package registry.
Frequently asked questions about inngest safety
Install (safety-checked)
Weekly Downloads
Version
3.50.0License
Apache-2.0Last Scanned
Trust Score
Capabilities
Connects to: api.inngest.com, app.inngest.com, beta.nextjs.org...
Spawns child processes
Accesses: NODE_ENV, PORT