next-router-mock

npm

Is next-router-mock safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for next-router-mock v1.0.5. Trust score: 65/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)

next-router-mock 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.

next-router-mock Capabilities & Permissions

What next-router-mock 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.

base.comgithub.comjasonformat.com
Protocols: https

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for next-router-mock

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

next-router-mock Documentation & Source Code

For the full next-router-mock README, API documentation, and source code, visit the official package registry.

Frequently asked questions about next-router-mock safety

Weekly Downloads

694.9K

Version

1.0.5

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: base.com, github.com, jasonformat.com

Environment

Accesses: NODE_ENV

Is next-router-mock Safe? | npm Safety Scan - brin