Skills npm-git-install
📦
npm-git-install
Content revision r1 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables
Install npm Packages from Git Repositories
Teams often need packages from branches, forks, or private GitHub repositories before they reach npm. This skill explains npm Git URL formats, authentication options, install checks, and common fixes.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "npm-git-install" from https://skillstore.io/skills/supercent-io-npm-git-install.md and its manifest at https://skillstore.io/api/skills/supercent-io-npm-git-install/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "npm-git-install". I need to install a package from a GitHub branch.
Expected outcome:
The assistant asks for the repository and branch, recommends pinning a tag or commit for production, and gives a concise install command.
Using "npm-git-install". My private GitHub package fails during npm install.
Expected outcome:
The assistant separates authentication checks from package build checks, then suggests SSH, token, and verbose logging steps.
Using "npm-git-install". A global Git package command is not found after install.
Expected outcome:
The assistant checks the global npm prefix, package bin entry, shell PATH, and install location before changing system permissions.
Security Audit
High Riskv6 • 7/9/2026 Open versioned report
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
31
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
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
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
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 View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/supercent-io-npm-git-install/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/supercent-io-npm-git-install?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/supercent-io-npm-git-install?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supercent-io-npm-git-install/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/supercent-io-npm-git-install.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
supercent-io. (2026). npm-git-install security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supercent-io-npm-git-install/audits/6BibTeX citation
@techreport{supercent-io-supercent-io-npm-git-install-2026,
author = {supercent-io},
title = {npm-git-install security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/supercent-io-npm-git-install/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "npm-git-install security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "supercent-io"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/supercent-io-npm-git-install/audits/6"
identifiers:
- type: other
value: "skillstore:supercent-io-npm-git-install:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Install an unreleased package version
Use a branch, tag, or commit reference when a package update is not published to npm yet.
Use a private GitHub package
Set up SSH or token-based authentication for an internal repository dependency.
Troubleshoot Git URL installs
Check install paths, prepare script failures, Git availability, cache issues, and global binaries.
Try These Prompts
Install from GitHub
Help me install an npm package from a GitHub repository. Ask for the owner, repo, and branch or tag before giving commands.
Pin a Dependency
Review my npm Git dependency and suggest a pinned tag or commit workflow that keeps installs reproducible.
Set Up Private Access
Guide me through installing an npm package from a private GitHub repository using SSH or token-based access.
Diagnose Install Failures
Help me diagnose an npm Git install failure. Include checks for Git, authentication, prepare scripts, cache, and global paths.
Best Practices
- Pin production dependencies to a tag or commit instead of a moving branch.
- Review repository trust, package scripts, and lockfile changes before installing from GitHub.
- Use least-privilege credentials and keep tokens out of command history, logs, and package files.
Avoid
- Do not install from unknown repositories with global permissions.
- Do not place personal access tokens directly in dependency URLs.
- Do not use sudo or recursive ownership changes before checking safer npm prefix options.
Frequently Asked Questions
Can this install packages that are not published to npm?
Yes. npm can install directly from GitHub repositories when the package has a valid package definition.
Should I use a branch name in production?
Use a tag or commit for production. Branches can move and make builds hard to reproduce.
Does this skill authenticate to private repositories for me?
No. It explains options, but users must manage SSH keys, tokens, and permissions themselves.
Can Git URL installs run package scripts?
Yes. npm can run lifecycle scripts such as prepare, so review the repository before installation.
Is global installation required?
No. Use local dependencies when possible, and use global installs only for trusted command line tools.
What tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.
Developer Details
Author
supercent-ioLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Maintenance freshness
7/18/2026
Usage
5 downloads · 125 views
File structure
📄 SKILL.md