Skip to content
TrustedSkillsbeta
Back to all skills

Npm Trusted Publishing

Checked
pr-pm·vlatest·backend·MIT

Ensures npm packages adhere to security best practices & guidelines, boosting developer trust and reducing vulnerabilities.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pr-pm/prpm --skill npm-trusted-publishing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pr-pm

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pr-pm/prpm at 50dfeb8f46.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
50dfeb8f46
Manifest
.claude/skills/npm-trusted-publishing/SKILL.md
Scanned
1 file, 109 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to publish packages to the npm registry using trusted publishing. It allows you to specify a list of publishers that are authorized to publish packages, enhancing security and preventing unauthorized modifications. This feature is particularly useful for organizations wanting tighter control over their published artifacts.

When to use it

  • Secure Package Publishing: When an organization needs to restrict who can publish npm packages.
  • Automated CI/CD Pipelines: Integrate with automated build systems to ensure only authorized publishers can release new versions.
  • Internal Registry Management: Control publishing access within a private or internal npm registry environment.
  • Preventing Malicious Packages: Limit the risk of compromised accounts publishing malicious packages.

Key capabilities

  • Trusted Publishing configuration
  • Package publication authorization
  • Registry access control

Example prompts

  • "Publish this package to npm, ensuring only authorized publishers can do so."
  • "Verify that my team members are listed as trusted publishers for our project's registry."
  • "What is the current list of trusted publishers configured for this npm scope?"

Tips & gotchas

This skill requires a properly configured npm registry with Trusted Publishing enabled. Ensure you have appropriate permissions within the registry to manage trusted publishers.