@hdnet/semantic-release-config
npmIs @hdnet/semantic-release-config safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @hdnet/semantic-release-config v3.3.3. Trust score: 55/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)
@hdnet/semantic-release-config 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.
@hdnet/semantic-release-config Capabilities & Permissions
What @hdnet/semantic-release-config 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 @hdnet/semantic-release-config
Good instructions lead to good results. brin adds @hdnet/semantic-release-config 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 →
@hdnet/semantic-release-config Documentation & Source Code
For the full @hdnet/semantic-release-config README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @hdnet/semantic-release-config safety
Install (safety-checked)
Weekly Downloads
Version
3.3.3Last Scanned
Trust Score
Capabilities
Accesses: ISSUE_PREFIX, ISSUE_URL_FORMAT, NEXT_BRANCH...