libnpmpublish

npm

Is libnpmpublish safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for libnpmpublish v11.1.3. 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)

libnpmpublish 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.

libnpmpublish Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

ACTIONS_ID_TOKEN_REQUEST_URLSIGSTORE_ID_TOKEN

AGENTS.md for libnpmpublish

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

libnpmpublish Documentation & Source Code

For the full libnpmpublish README, API documentation, and source code, visit the official package registry.

Frequently asked questions about libnpmpublish safety

Weekly Downloads

2.1M

Version

11.1.3

License

ISC

Last Scanned

Feb 1, 2026

Trust Score

85/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: ACTIONS_ID_TOKEN_REQUEST_URL, SIGSTORE_ID_TOKEN

Is libnpmpublish Safe? | npm Safety Scan - brin