📦
Audit History
npm-git-install - 6 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v6 Latest | Jul 9, 2026, 09:11 AM | 4 confirmed | 31 | No capability change |
| v5 | Jul 9, 2026, 09:11 AM | 4 confirmed | 31 | No capability change |
| v4 | Jul 7, 2026, 04:54 AM | 5 confirmed | 20 | Contains scripts |
| v3 | Jun 30, 2026, 09:45 PM | No confirmed findings | 4 | No capability change |
| v2 | Jun 30, 2026, 09:45 PM | No confirmed findings | 4 | Contains scripts |
| v1 | Mar 20, 2026, 08:20 AM | No confirmed findings | 2 | Baseline |
Audit version 6 Latest
Jul 9, 2026, 09:11 AM
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.
2
Files scanned
388
Lines analyzed
39
Review items
0
False positives ignored
Confirmed security concerns (4)
High
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.
High
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.
High
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.
High
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.
Capability review items (31)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
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
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
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
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
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
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
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
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
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
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
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
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
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
Hardcoded URL · 2 occurrences
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 Factors
⚙️ External commands (50)
SKILL.md:28-30 SKILL.md:30-34 SKILL.md:34-46 SKILL.md:46-50 SKILL.md:50-52 SKILL.md:52-56 SKILL.md:56-58 SKILL.md:58-66 SKILL.md:66-78 SKILL.md:78-82 SKILL.md:82-91 SKILL.md:91-97 SKILL.md:97-110 SKILL.md:110-116 SKILL.md:116 SKILL.md:117 SKILL.md:118 SKILL.md:126-134 SKILL.md:134-138 SKILL.md:138-147 SKILL.md:147-155 SKILL.md:155-165 SKILL.md:165-169 SKILL.md:169-179 SKILL.md:179-183 SKILL.md:183-186 SKILL.md:186-194 SKILL.md:194-203 SKILL.md:203-207 SKILL.md:207-216 SKILL.md:216-220 SKILL.md:220-228 SKILL.md:228-232 SKILL.md:232-238 SKILL.md:238-242 SKILL.md:242-249 SKILL.md:249-257 SKILL.md:257-264 SKILL.md:264-268 SKILL.md:268-274 SKILL.md:274-278 SKILL.md:278-280 SKILL.md:280-288 SKILL.md:288-294 SKILL.md:294-298 SKILL.md:298-317 SKILL.md:317-325 SKILL.md:325-334 SKILL.md:334-377 SKILL.md:377
🌐 Network access (23)
📁 Filesystem access (20)
🔑 Env variables (3)
Audited by: codex
Jul 9, 2026, 09:11 AM
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.
2
Files scanned
388
Lines analyzed
39
Review items
0
False positives ignored
Confirmed security concerns (4)
High
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.
High
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.
High
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.
High
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.
Capability review items (31)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
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
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
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
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
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
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
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
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
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
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
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
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
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
Hardcoded URL · 2 occurrences
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 Factors
⚙️ External commands (50)
SKILL.md:28-30 SKILL.md:30-34 SKILL.md:34-46 SKILL.md:46-50 SKILL.md:50-52 SKILL.md:52-56 SKILL.md:56-58 SKILL.md:58-66 SKILL.md:66-78 SKILL.md:78-82 SKILL.md:82-91 SKILL.md:91-97 SKILL.md:97-110 SKILL.md:110-116 SKILL.md:116 SKILL.md:117 SKILL.md:118 SKILL.md:126-134 SKILL.md:134-138 SKILL.md:138-147 SKILL.md:147-155 SKILL.md:155-165 SKILL.md:165-169 SKILL.md:169-179 SKILL.md:179-183 SKILL.md:183-186 SKILL.md:186-194 SKILL.md:194-203 SKILL.md:203-207 SKILL.md:207-216 SKILL.md:216-220 SKILL.md:220-228 SKILL.md:228-232 SKILL.md:232-238 SKILL.md:238-242 SKILL.md:242-249 SKILL.md:249-257 SKILL.md:257-264 SKILL.md:264-268 SKILL.md:268-274 SKILL.md:274-278 SKILL.md:278-280 SKILL.md:280-288 SKILL.md:288-294 SKILL.md:294-298 SKILL.md:298-317 SKILL.md:317-325 SKILL.md:325-334 SKILL.md:334-377 SKILL.md:377
🌐 Network access (23)
📁 Filesystem access (20)
🔑 Env variables (3)
Audited by: codex
Jul 7, 2026, 04:54 AM
Most static findings are Markdown syntax, placeholder paths, or documentation links rather than executable code. Confirmed risks remain around privileged commands, token handling, npmrc configuration, authenticated Git installs, mutable remote packages, and persistent shell or credential configuration. No prompt injection attempt was found in the reviewed skill text.
2
Files scanned
388
Lines analyzed
29
Review items
2
False positives ignored
Confirmed security concerns (5)
High
NPM config file (may contain tokens)
### .npmrc Configuration
The section explicitly covers .npmrc authentication configuration. npm config files may contain tokens and need least-privilege handling.
High
NPM config file (may contain tokens)
# ~/.npmrc
The guide names ~/.npmrc immediately before an auth token entry. This is a real credential-handling surface, even though the token is variable-based.
High
Mutable Git Install Can Execute Remote Package Scripts
The guide explains that npm Git installs clone a repository, install dependencies, and run a prepare script. Examples that install from main increase supply-chain risk because remote lifecycle scripts can change over time.
The file explicitly documents npm running prepare during Git installs and shows mutable main-branch installs. This is legitimate package-manager behavior, but it is a clear remote code execution surface.
High
Plaintext Credential Helper Recommendation
The authentication troubleshooting section recommends the Git credential helper named store. That helper can persist credentials in plaintext on disk on common Git installations.
The recommendation is directly present in the troubleshooting section. The security impact depends on the platform, but credential.helper store is a known plaintext storage risk.
Low
System reconnaissance
sudo chown -R $(whoami) /usr/local/lib/node_modules
The command runs whoami as part of a privileged ownership change. The reconnaissance value is limited, but it does inspect local account identity.
Capability review items (20)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Shell command substitution
sudo chown -R $(whoami) /usr/local/lib/node_modules
The command substitution is embedded in a sudo chown command that changes ownership under /usr/local. The whoami input is fixed, but the privileged filesystem change is real operational risk.
High
sudo privilege escalation
sudo chown -R $(whoami) /usr/local/lib/node_modules
The guide recommends sudo chown against a global Node.js directory. This can alter system package ownership and should require explicit user approval.
High
sudo privilege escalation
sudo apt-get install git
The guide recommends sudo apt-get install git, which invokes a privileged package manager operation. It is common administration, but still changes the host system.
High
Hardcoded URL
npm install git+https://<token>@github.com/owner/private-repo.git
The install URL places an authentication token directly in the URL. Token-bearing URLs can leak through shell history, process listings, lockfiles, or logs.
High
Hardcoded URL
npm install git+https://${GITHUB_TOKEN}@github.com/owner/private-repo.git
The command expands GITHUB_TOKEN into a Git URL. Even when sourced from an environment variable, the final URL can leak through logs or process metadata.
High
Hidden file in home directory
# ~/.npmrc
The guide introduces ~/.npmrc for token configuration. That hidden home file often stores authentication material and should be handled carefully.
High
Hidden file in home directory
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
The command appends a PATH export to ~/.bashrc, creating a persistent shell startup change. Persistent shell configuration edits require explicit consent.
High
Hidden file access
# ~/.npmrc
The ~/.npmrc example is tied to GitHub token authentication. Accessing or editing this file can affect package credentials for the user account.
High
Git platform tokens
export GITHUB_TOKEN=ghp_xxxxxxxxxxxx
The guide instructs users to export a GitHub token into the environment. Real tokens are high-value credentials and can leak to child processes.
High
Git platform tokens
npm install git+https://${GITHUB_TOKEN}@github.com/owner/private-repo.git
The install command expands GITHUB_TOKEN into a network URL. That can expose the token in command history, logs, or process metadata.
High
Git platform tokens
//github.com/:_authToken=${GITHUB_TOKEN}
The npmrc example configures GitHub authentication using GITHUB_TOKEN. Misconfigured npmrc files can persist or disclose package access credentials.
Medium
Hardcoded URL · 2 occurrences
npm install -g git+https://github.com/JEO-tech-ai/supercode.git#main
This installs a hardcoded external GitHub repository from the mutable main branch. Git-based npm installs can execute package lifecycle scripts from remote code.
Medium
Hardcoded URL
npm install -g git+https://github.com/JEO-tech-ai/supercode.git#main --verbose
This repeats the hardcoded external repository install with verbose output. It fetches remote package code and may expose installation details in logs.
Medium
Hardcoded URL
"supercode": "git+https://github.com/JEO-tech-ai/supercode.git#main",
The dependency example pins a package name to a hardcoded external GitHub repository on main. That creates supply-chain exposure if copied into package.json.
Medium
Hardcoded URL
npm install git+https://... --verbose 2>&1 | tee npm-install.log
The verbose install command writes output to a log file. If used with tokenized Git URLs from the same guide, credentials or repository metadata may be persisted.
Medium
SSH protocol URL
npm install -g git+ssh://git@github.com:JEO-tech-ai/supercode.git#main
The SSH install uses the user's GitHub SSH identity to fetch remote package code. That is an intended workflow, but it relies on authenticated network access.
Medium
SSH protocol URL
"my-package": "git+ssh://git@github.com:owner/repo.git#v1.0.0",
The dependency example stores an SSH Git URL in package metadata. It can trigger authenticated network access and remote package execution during install.
Medium
SSH protocol URL
npm install git+ssh://git@github.com:owner/private-repo.git
The private repository install uses SSH authentication. It is legitimate, but it lets npm fetch and build code using the user's GitHub identity.
Medium
Hidden file access
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
The command writes to ~/.bashrc to alter future shells. The content is simple PATH configuration, but it is still a persistent hidden-file modification.
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Critical
SSH directory access
cat ~/.ssh/id_ed25519.pub
Force-confirmed sensitive/critical static finding; AI dismissal overridden.
Critical
SSH private key file
cat ~/.ssh/id_ed25519.pub
Force-confirmed sensitive/critical static finding; AI dismissal overridden.
Risk Factors
⚙️ External commands (54)
SKILL.md:28-30 SKILL.md:30-34 SKILL.md:34-46 SKILL.md:46-50 SKILL.md:50-52 SKILL.md:52-56 SKILL.md:56-58 SKILL.md:58-66 SKILL.md:66-78 SKILL.md:78-82 SKILL.md:82-91 SKILL.md:91-97 SKILL.md:97-110 SKILL.md:110-116 SKILL.md:116 SKILL.md:117 SKILL.md:118 SKILL.md:126-134 SKILL.md:134-138 SKILL.md:138-147 SKILL.md:147-155 SKILL.md:155-165 SKILL.md:165-169 SKILL.md:169-179 SKILL.md:179-183 SKILL.md:183-186 SKILL.md:186-194 SKILL.md:194-203 SKILL.md:203-207 SKILL.md:207-216 SKILL.md:216-220 SKILL.md:220-228 SKILL.md:228-232 SKILL.md:232-238 SKILL.md:238-242 SKILL.md:242-249 SKILL.md:249-257 SKILL.md:257-264 SKILL.md:264-268 SKILL.md:268-274 SKILL.md:274-278 SKILL.md:278-280 SKILL.md:280-288 SKILL.md:288-294 SKILL.md:294-298 SKILL.md:298-317 SKILL.md:317-325 SKILL.md:325-334 SKILL.md:334-377 SKILL.md:377 SKILL.md:196 SKILL.md:194-203 SKILL.md:196 SKILL.md:212
🌐 Network access (23)
📁 Filesystem access (20)
🔑 Env variables (3)
Detected Patterns
System reconnaissance
Audited by: codex
Jun 30, 2026, 09:45 PM
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.
2
Files scanned
388
Lines analyzed
9
Review items
2
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
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
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
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
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.
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Low
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
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.
Risk Factors
⚡ Contains scripts (2)
🌐 Network access (6)
📁 Filesystem access (6)
🔑 Env variables (2)
Detected Patterns
npm install git+ URL Patternsudo and Global Configuration Commands
Audited by: codex
Jun 30, 2026, 09:45 PM
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.
2
Files scanned
388
Lines analyzed
9
Review items
2
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
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
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
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
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.
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Low
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
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.
Risk Factors
⚡ Contains scripts (2)
🌐 Network access (6)
📁 Filesystem access (6)
🔑 Env variables (2)
Detected Patterns
npm install git+ URL Patternsudo and Global Configuration Commands
Audited by: codex
Mar 20, 2026, 08:20 AM
This skill is documentation-only (markdown guide). Static analyzer flagged 119 patterns in code examples, but all are FALSE POSITIVES. The skill teaches legitimate npm/git workflows. Minor risk: documents sudo usage and credential handling patterns, but explicitly recommends secure practices (env vars over hardcoded tokens, SSH over passwords).
2
Files scanned
388
Lines analyzed
6
Review items
3
False positives ignored
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
Documentation References sudo Commands
The skill documents sudo usage for fixing npm permissions (line 196). While this is legitimate system administration, users could misuse sudo. The skill does recommend safer alternatives (~/.npm-global).
sudo commands present in documentation examples, but skill explicitly recommends non-sudo alternatives as preferred approach
Low
Documents Credential Handling Patterns
The skill documents GitHub token usage and SSH key setup. While it recommends secure practices (env vars, SSH), providing these patterns could be misused if users don't follow the security guidance.
Credential patterns documented but skill explicitly recommends secure handling via environment variables and SSH keys
Static false positives ignored (3)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Low
Static Analyzer False Positives - Command Patterns in Documentation
61 'external_commands' detections are markdown code examples, not executable skill code. Pattern matches like $(whoami) and backticks are bash examples in documentation context.
All detected patterns are in markdown code blocks - this is documentation teaching users commands, not a skill that executes code
Low
Static Analyzer False Positives - URL Patterns
23 'network' detections are documentation URLs (github.com, npm docs, stackoverflow) and git URL examples. These are reference links, not network calls made by the skill.
URLs are documentation references and git URL syntax examples, not actual network requests
Low
Static Analyzer False Positives - Filesystem Paths
24 'filesystem' detections include /tmp paths, ~/.ssh, ~/.npmrc references. These are documentation examples showing where npm/git store files, not actual file operations by the skill.
File paths appear in documentation examples explaining npm/git behavior, not skill file operations
Risk Factors
⚙️ External commands (2)
🌐 Network access (2)
📁 Filesystem access (2)
🔑 Env variables (1)
Audited by: claude