@petercjl/npm-release-kit
Token-free npm releases through GitHub Actions trusted publishing, with portable Agent skills.
No outside reports on file
@petercjl/npm-release-kit connects to external service APIs and requires API keys or tokens; 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
- CredentialsRequires API key or tokenREVIEW
- Package sourcenpm (@petercjl/npm-release-kit)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y @petercjl/npm-release-kitEverything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: D (from public signals such as stars and downloads, not a code review). Graded 2026-10-21.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About @petercjl/npm-release-kit
@petercjl/npm-release-kit is an agent skill focused on Developer tools: Token-free npm releases through GitHub Actions trusted publishing, with portable Agent skills.
It is published on npm as @petercjl/npm-release-kit and hosted on GitHub at petercjl/npm-release-kit (last repository push on 2026-09-30). Based on its public metadata, its operational scope includes: connects to outside service api, requires api key or token.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
npm command
npx -y @petercjl/npm-release-kitWhy this grade
Signal-based grade (1/7 points): public source code. 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.
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.
- Credential & token exposure: Requires API keys or secrets in configuration. Store credentials in environment variables with read-only or minimum required scopes and rotate them regularly.
- Dependency & version pinning: Distributed via npm (@petercjl/npm-release-kit). 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 @petercjl/npm-release-kit?
Install @petercjl/npm-release-kit with npm install @petercjl/npm-release-kit or run it directly with npx -y @petercjl/npm-release-kit. For agent integration and configuration flags, see the documentation at github.com/petercjl/npm-release-kit. Pin an exact version and pass --ignore-scripts if you want to block post-install hooks.
Are there security reports about @petercjl/npm-release-kit?
No reports found for this package in our research (last checked 2026-10-30). @petercjl/npm-release-kit currently holds Grade D (High 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 @petercjl/npm-release-kit actively maintained?
We do not have star or download counts on file for @petercjl/npm-release-kit yet (listing refreshed 2026-10-28). Check the commit history and open issues at github.com/petercjl/npm-release-kit before relying on it.
What are alternatives to @petercjl/npm-release-kit?
You can compare @petercjl/npm-release-kit 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 @petercjl/npm-release-kit? 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/petercjl-npm-release-kit)HTML embed:
<a href="https://agentarmorhq.com/skills/petercjl-npm-release-kit"><img src="https://agentarmorhq.com/api/badge/petercjl-npm-release-kit" alt="AgentArmorHQ Risk Grade for @petercjl/npm-release-kit" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "petercjl-npm-release-kit"- Compare @petercjl/npm-release-kit →
- Add to a team allowlist
- Claude and terminal guide →
- Download the PDF guide
Share with your security lead
Need sign-off to use @petercjl/npm-release-kit? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: @petercjl/npm-release-kit
- **Listing URL:** https://agentarmorhq.com/skills/petercjl-npm-release-kit
- **Type:** AI agent skill
- **Risk Grade:** Grade D (High 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:** Requires API key or token
- **Package source:** npm (@petercjl/npm-release-kit)
#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts @petercjl/npm-release-kit`
- **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
- Publisher
- petercjl
- Source code
- github.com/petercjl/npm-release-kit
- Install command
- npm install @petercjl/npm-release-kit
- Est. context load
- ~54 tokens idle · ~950 tokens when active (on-demand skill)
- Last updated
- 2026-10-28
- Last graded
- 2026-10-21
Community
Discussions for @petercjl/npm-release-kit
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