Versioned security assessment

Report ID: SA-E78576F5

6/30/2026, 9:45:56 PM

npm-git-install security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
npm-git-install
Version
v3
Maintainer
supercent-io
Source
github.com/supercent-io/skills-template/tree/main/.agent-skills/npm-git-install/
Coverage
2 Files scanned · 388 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static analysis found many command, network, filesystem, and credential patterns, but most are markdown examples in a documentation skill rather than executable code. The confirmed risks are operational: Git-based npm installs can execute package lifecycle scripts, token-based authentication can leak credentials, and global setup commands can alter user systems. No evidence found of prompt injection or malicious hidden behavior.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

2 Files scanned · 388 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Observed in 2 evidence locations

Network access

May connect to external services.

Observed in 6 evidence locations

Filesystem access

May read or write local files.

Observed in 6 evidence locations

Env variables

May read values from the process environment.

Observed in 2 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 10 evidence locations

Capability review items (4)
Medium
SKILL.md:29SKILL.md:73-74SKILL.md:84-88SKILL.md:257-260
Supply Chain Execution Through Git npm Installs
The skill instructs users to install packages directly from GitHub and explains that npm may run prepare scripts during installation. This is legitimate package-management guidance, but untrusted repositories can execute install-time code and should be pinned and reviewed.
The markdown context clearly documents npm Git installs and npm lifecycle behavior. The risk is real for untrusted Git repositories, although it is not evidence of malicious intent in the skill itself.
Medium
SKILL.md:173-178SKILL.md:181-185SKILL.md:224-227
Credential Handling Guidance Can Expose Tokens
The skill shows token-based GitHub installation, a GITHUB_TOKEN environment variable, an .npmrc token entry, and credential helper storage. These are common workflows, but tokens in URLs, shell history, logs, or persistent config can leak repository access.
The skill explicitly discusses GitHub tokens and credential storage. It also warns against hardcoding tokens, so the issue is cautionary rather than malicious.
Medium
SKILL.md:51-57SKILL.md:196-202SKILL.md:212SKILL.md:224-227
Global Installation and Permission Commands Alter System State
The guide includes global npm installs, sudo package installation, sudo ownership changes, shell profile edits, and global Git credential configuration. These commands are expected for setup guidance but can change system security posture if copied without review.
The cited commands are present and can materially affect a user machine. The surrounding text frames them as troubleshooting instructions, so this is an elevated-use risk, not confirmed abuse.
Low
SKILL.md:155-164
SSH Private Key Finding Points to Public Key Output
The SSH-key section reads ~/.ssh/id_ed25519.pub so the user can register a public key on GitHub. This is not private-key disclosure, although users should still avoid sharing private key material.
The filename ends in .pub and the surrounding steps describe registering a public SSH key. No evidence found of reading a private key file.

Risk findings

Confirmed security concerns are separated from items that still need review.

No confirmed security findings were recorded for this completed audit.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
SKILL.md:28-30SKILL.md:82-90SKILL.md:194-203
Static Command Execution Findings Are Markdown Examples
The many shell-command detections occur inside documentation code fences and command examples. The skill does not include an executable script that automatically runs these commands.
The file is a Markdown guide, and the detected commands are inside fenced examples. No evidence found of automatic command execution by the skill.
Low
SKILL.md:90SKILL.md:373-374
Path Traversal and Symlink Detections Are Documentation Examples
The symlink command is part of an explanation of npm internals, and the ../ paths are related-skill links. No evidence found that the skill uses these paths to access files outside the workspace.
The suspicious paths are visible in markdown context and are not part of executable code. They are best classified as false positives from static pattern matching.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable