git-node-platform
A js-git platform implementation for node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:ssh-key-access | AI (semgrep): This package is a js-git SSH transport layer; reading ~/.ssh/id_rsa as a default key is standard SSH client behavior, not credential theft. Key is used locally for SSH auth, not exfiltrated. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 1 / 0 | |
| 0.1.3 | 1 / 0 | |
| 0.1.2 | 1 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 1 / 0 |
v0.1.4
2 findingsAccessing SSH keys — strong indicator of credential theft 16 | else if (opts.privateKey) config.privateKey = opts.privateKey; 17 | else { > 18 | config.privateKey = require('fs').readFileSync(process.env.HOME + "/.ssh/id_rsa"); 19 | } 20 | if (opts.pathname.substr(0, 2) === "/:") opts.pathname = opts.pathname.substr(2);
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.