@evgenest/safe-release
Claude Code skill for safe GitHub releases using staged pre-release/beta workflows
No outside reports on file
@evgenest/safe-release connects to external service APIs; restrict its folder reach, network access, and credentials before installing.
Based on public adoption and transparency signals as of Oct 21, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachConnects to outside service APINOTED
- CredentialsNo API token requiredLOW
- Package sourcenpm (@evgenest/safe-release)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y @evgenest/safe-releaseAbout @evgenest/safe-release
@evgenest/safe-release is an agent skill focused on Developer tools: Claude Code skill for safe GitHub releases using staged pre-release/beta workflows.
It is published on npm as @evgenest/safe-release. Based on its public metadata, its operational scope includes: connects to outside service api.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
npm command
npx -y @evgenest/safe-releaseWhy this grade
Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- Listing last refreshed
- 2026-10-28
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
No reports found for this package in our research (last checked 2026-10-29).
Risks to watch for
- External API & account scope: Connects to third-party service APIs. Use a dedicated, least-privilege token scoped only to the workspaces or repositories this tool needs.
- Dependency & version pinning: Distributed via npm (@evgenest/safe-release). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install @evgenest/review-release?
Install @evgenest/review-release with npm install @evgenest/review-release or run it directly with npx -y @evgenest/review-release. Pin an exact version and pass --ignore-scripts if you want to block post-install hooks.
Are there security reports about @evgenest/review-release?
No reports found for this package in our research (last checked 2026-10-29). @evgenest/review-release currently holds Grade F (Many risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is @evgenest/review-release actively maintained?
We do not have star or download counts on file for @evgenest/review-release yet (listing refreshed 2026-10-28). Check the commit history and open issues before relying on it.
What are alternatives to @evgenest/review-release?
You can compare @evgenest/review-release side by side with other GitHub skills in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.
README badge and team notes
Maintain or use @evgenest/safe-release? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/evgenest-safe-release)HTML embed:
<a href="https://agentarmorhq.com/skills/evgenest-safe-release"><img src="https://agentarmorhq.com/api/badge/evgenest-safe-release" alt="AgentArmorHQ Risk Grade for @evgenest/safe-release" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "evgenest-safe-release"- Compare @evgenest/safe-release →
- Add to a team allowlist
- Claude and terminal guide →
- Download the PDF guide
Share with your security lead
Need sign-off to use @evgenest/safe-release? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: @evgenest/safe-release
- **Listing URL:** https://agentarmorhq.com/skills/evgenest-safe-release
- **Type:** AI agent skill
- **Risk Grade:** Grade F (Many risk signals)
- **Outside Security Advisories on File:** 0
#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Connects to outside service API
- **Credentials:** No API token required
- **Package source:** npm (@evgenest/safe-release)
#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts @evgenest/safe-release`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 21, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- AI agent skill
- Install command
- npm install @evgenest/safe-release
- Est. context load
- ~50 tokens idle · ~900 tokens when active (on-demand skill)
- Last updated
- 2026-10-28
- Last graded
- 2026-10-21
Community
Discussions for @evgenest/safe-release
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude