static-module

npm

Is static-module safe to use?

The latest brin safety scan flagged static-module v3.0.4 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 85/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

static-module Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • Can spawn child processes

brin Recommendations

  • This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add static-module 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.

static-module Capabilities & Permissions

What static-module can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Filesystem Access

Reads from the filesystem.

/usr/ (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for static-module

Good instructions lead to good results. brin adds static-module 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 →

static-module Documentation & Source Code

For the full static-module README, API documentation, and source code, visit the official package registry.

Frequently asked questions about static-module safety

Weekly Downloads

710.0K

Version

3.0.4

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is static-module Safe? | npm Safety Scan - brin