brin
brin

w3c-keyname

npm

Is w3c-keyname safe to use?

The latest brin safety scan flagged w3c-keyname v2.2.8 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

w3c-keyname 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 w3c-keyname 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.

w3c-keyname Capabilities & Permissions

What w3c-keyname 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.

AGENTS.md for w3c-keyname

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

w3c-keyname Documentation & Source Code

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

View on npmView SourceHomepage

Frequently asked questions about w3c-keyname safety

Weekly Downloads

7.7M

Version

2.2.8

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is w3c-keyname Safe? | npm Safety Scan - brin