@storybook/nextjs
npmIs @storybook/nextjs safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @storybook/nextjs v10.2.7. Trust score: 85/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)
@storybook/nextjs Passed Security Checks
No security concerns detected
0
0
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.
@storybook/nextjs Capabilities & Permissions
What @storybook/nextjs can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for @storybook/nextjs
Good instructions lead to good results. brin adds @storybook/nextjs 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 →
@storybook/nextjs Documentation & Source Code
For the full @storybook/nextjs README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @storybook/nextjs safety
Install (safety-checked)
Weekly Downloads
Version
10.2.7License
MITLast Scanned
Trust Score
Capabilities
Spawns child processes
Accesses: NODE_ENV, VITEST, __NEXT_NEW_LINK_BEHAVIOR...