in-publish
npmIs in-publish safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for in-publish v2.0.1. 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)
in-publish 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.
in-publish Capabilities & Permissions
What in-publish 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.
AGENTS.md for in-publish
Good instructions lead to good results. brin adds in-publish 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 →
in-publish Documentation & Source Code
For the full in-publish README, API documentation, and source code, visit the official package registry.
Frequently asked questions about in-publish safety
Install (safety-checked)
Weekly Downloads
Version
2.0.1License
ISCLast Scanned
Trust Score
Capabilities
Accesses: npm_command, npm_config_argv