Versioned security assessment

Report ID: SA-3E4B6C31

7/9/2026, 9:11:54 AM

npm-git-install security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Latest published report
Skill name
npm-git-install
Version
v6
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

Highest confirmed finding severity

High

4 confirmed security findings require attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

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

This documentation-focused skill is not malicious, and many backtick detections are Markdown false positives. Remaining risks include GitHub package installs, lifecycle scripts, token authentication, .npmrc edits, global binary linking, and privileged troubleshooting commands.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

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

35 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

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  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.

Not recorded by this audit

Network access

May connect to external services.

Observed in 23 evidence locations

Filesystem access

May read or write local files.

Observed in 12 evidence locations

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 52 evidence locations

Capability review items (31)
High
SKILL.md:196
sudo privilege escalation
sudo chown -R $(whoami) /usr/local/lib/node_modules
The command uses sudo to recursively change ownership under /usr/local/lib/node_modules. If followed without review, it changes system-owned package files and can weaken local integrity.
High
SKILL.md:212
sudo privilege escalation
sudo apt-get install git
The command installs system packages with sudo apt-get. This is a common setup step, but it grants elevated privileges and should require explicit user confirmation.
High
SKILL.md:174
Hardcoded URL
npm install git+https://<token>@github.com/owner/private-repo.git
The install URL includes a GitHub token placeholder, which can leak through shell history, process listings, npm logs, or copied package metadata. The context is legitimate private repo access but the pattern is sensitive.
High
SKILL.md:178
Hardcoded URL
npm install git+https://${GITHUB_TOKEN}@github.com/owner/private-repo.git
The install URL includes a GitHub token placeholder, which can leak through shell history, process listings, npm logs, or copied package metadata. The context is legitimate private repo access but the pattern is sensitive.
High
SKILL.md:184
Hidden file in home directory
# ~/.npmrc
The skill directs configuration in ~/.npmrc, a hidden file that commonly stores package registry credentials. Mishandling this file can expose tokens.
High
SKILL.md:201
Hidden file in home directory
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
The guidance modifies or sources ~/.bashrc, a persistent shell startup file. Changing startup files can affect future shell behavior and should be reviewed.
High
SKILL.md:202
Hidden file in home directory
source ~/.bashrc
The guidance modifies or sources ~/.bashrc, a persistent shell startup file. Changing startup files can affect future shell behavior and should be reviewed.
High
SKILL.md:184
Hidden file access
# ~/.npmrc
The .npmrc path is security-sensitive because it may contain registry or GitHub tokens. The nearby example configures token-based authentication.
High
SKILL.md:90
Symlink creation
ln -s ../lib/node_modules/repo/bin/cli.js /usr/local/bin/repo
The example creates a symlink into /usr/local/bin, which can affect global command resolution. Although illustrative, this is a security-sensitive filesystem operation.
High
SKILL.md:177
Git platform tokens
export GITHUB_TOKEN=ghp_xxxxxxxxxxxx
The line handles GITHUB_TOKEN or passes it into npm/GitHub authentication. These values are secrets and can leak through logs, shell history, or configuration files if mishandled.
High
SKILL.md:178
Git platform tokens
npm install git+https://${GITHUB_TOKEN}@github.com/owner/private-repo.git
The line handles GITHUB_TOKEN or passes it into npm/GitHub authentication. These values are secrets and can leak through logs, shell history, or configuration files if mishandled.
High
SKILL.md:185
Git platform tokens
//github.com/:_authToken=${GITHUB_TOKEN}
The line handles GITHUB_TOKEN or passes it into npm/GitHub authentication. These values are secrets and can leak through logs, shell history, or configuration files if mishandled.
Medium
SKILL.md:196
Shell command substitution
sudo chown -R $(whoami) /usr/local/lib/node_modules
The example uses $(whoami) inside a sudo chown command, so a shell expansion is performed before changing ownership. It is troubleshooting guidance, but it is still security-sensitive command execution.
Medium
SKILL.md:36
Hardcoded URL
npm install -g git+https://github.com/JEO-tech-ai/supercode.git#main
The skill gives a concrete GitHub repository install or dependency example that fetches code from a moving branch. npm Git installs can execute package lifecycle scripts, so repository trust matters.
Medium
SKILL.md:57
Hardcoded URL
npm install -g git+https://github.com/JEO-tech-ai/supercode.git#main --verbose
The skill gives a concrete GitHub repository install or dependency example that fetches code from a moving branch. npm Git installs can execute package lifecycle scripts, so repository trust matters.
Medium
SKILL.md:129
Hardcoded URL
"supercode": "git+https://github.com/JEO-tech-ai/supercode.git#main",
The skill gives a concrete GitHub repository install or dependency example that fetches code from a moving branch. npm Git installs can execute package lifecycle scripts, so repository trust matters.
Medium
SKILL.md:290
Hardcoded URL
npm install -g git+https://github.com/JEO-tech-ai/supercode.git#main
The skill gives a concrete GitHub repository install or dependency example that fetches code from a moving branch. npm Git installs can execute package lifecycle scripts, so repository trust matters.
Medium
SKILL.md:51
SSH protocol URL
npm install -g git+ssh://git@github.com:JEO-tech-ai/supercode.git#main
The SSH Git URL is a real authenticated network install path for private or protected repositories. It is expected for the skill, but it depends on local SSH credentials and repository trust.
Medium
SKILL.md:130
SSH protocol URL
"my-package": "git+ssh://git@github.com:owner/repo.git#v1.0.0",
The SSH Git URL is a real authenticated network install path for private or protected repositories. It is expected for the skill, but it depends on local SSH credentials and repository trust.
Medium
SKILL.md:164
SSH protocol URL
npm install git+ssh://git@github.com:owner/private-repo.git
The SSH Git URL is a real authenticated network install path for private or protected repositories. It is expected for the skill, but it depends on local SSH credentials and repository trust.
Medium
SKILL.md:201
Hidden file access
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
The example writes to or sources ~/.bashrc, which changes user shell startup behavior. It is a common setup step but still needs user review.
Medium
SKILL.md:202
Hidden file access
source ~/.bashrc
The example writes to or sources ~/.bashrc, which changes user shell startup behavior. It is a common setup step but still needs user review.
Low
SKILL.md:29
Hardcoded URL
npm install git+https://github.com/<owner>/<repo>.git#<branch|tag|commit>
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:39
Hardcoded URL
npm install git+https://github.com/owner/repo.git#v1.0.0
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:42
Hardcoded URL
npm install git+https://github.com/owner/repo.git#abc1234
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:45
Hardcoded URL
npm install git+https://github.com/owner/repo.git
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:84
Hardcoded URL
git clone https://github.com/owner/repo.git /tmp/npm-xxx
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:237
Hardcoded URL
npm install git+https://... --verbose 2>&1 | tee npm-install.log
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:248
Hardcoded URL
npm install -g git+https://...
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:260
Hardcoded URL
npm install -g git+https://github.com/owner/repo.git#main
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.
Low
SKILL.md:273
Hardcoded URL
git ls-remote https://github.com/owner/repo.git HEAD
The line documents a GitHub network operation used by the skill. This is expected functionality, but it still requires external network access and trust in the referenced repository.

Risk findings

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

Confirmed security concerns (4)

RISK-001 High
SKILL.md:181
NPM config file (may contain tokens)
### .npmrc Configuration
The skill includes .npmrc token configuration for GitHub access. .npmrc can contain package registry credentials, so this guidance is security-sensitive.
RISK-002 High
SKILL.md:184
NPM config file (may contain tokens)
# ~/.npmrc
The skill includes .npmrc token configuration for GitHub access. .npmrc can contain package registry credentials, so this guidance is security-sensitive.
RISK-003 High
SKILL.md:36SKILL.md:73-77
Unreviewed GitHub Package Lifecycle Execution
The skill teaches npm installs from GitHub and explains that npm runs prepare scripts and registers global binaries. Installing unreviewed Git repositories can execute package code during installation.
The document explicitly combines GitHub install commands with npm prepare-script and global binary behavior. This is a clear supply-chain execution risk even though it is presented as legitimate package management guidance.
RISK-004 High
SKILL.md:224-225
Plaintext Git Credential Storage Guidance
The troubleshooting section recommends git credential.helper store for cached credentials. That helper can save credentials unencrypted on disk, creating a credential exposure risk.
The exact git credential.helper store command is present under credential caching. This is a known insecure storage option compared with OS keychain helpers.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    GitHub Git installs can execute unreviewed package code and lifecycle scripts.
    Require users to verify repository trust, review package scripts, and pin tags or commit SHAs before installing, especially for global installs.
  2. FIX-002
    High
    Token examples place GitHub credentials in URLs or npm configuration.
    Avoid token-in-URL examples, warn about shell history and logs, and prefer least-privilege tokens or SSH with clear secret-handling guidance.
  3. FIX-003
    High
    The guide recommends git credential.helper store for cached credentials.
    Remove that recommendation or clearly warn that it can store credentials unencrypted; prefer OS keychain-backed helpers.
  4. FIX-004
    High
    Troubleshooting examples use sudo and recursive ownership changes.
    Lead with user-level npm prefixes, nvm, or local installs, and require explicit confirmation before any privileged system change.
  5. FIX-005
    Medium
    SSH key setup shows reading from the ~/.ssh directory.
    Clarify that only public .pub files may be displayed, and never ask agents to inspect private SSH keys or include key material in logs.

Expert evidence

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

Artifact subject

Marketplace commit
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Content hash
c76befc45af13e35e77269ef5188ab64cb223020e45ec77517f44cee586f9eb6
Tree hash
4c3cdf404a88482a652f113ae00e687ad8365c29e4dd5ef112c86338bb7199a5
Skill path
skills/supercent-io/npm-git-install
Audit payload hash
0d7a3bccb27a0731c517188e2393fa9a

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.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest Source

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

Audit attestation: not_attestable