js-git MIT 29 versions

js-git

npm Repository Homepage

Git Implemented in JavaScript

29

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

creationix

Keywords

gitjs-git

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:bodec	AI (npm-metadata): Authored by creationix (same maintainer); long-standing git URL dependency pattern in this package.	ai	2026/04/24
npm-metadata	url-dep:pathjoin	AI (npm-metadata): Authored by creationix (same maintainer); long-standing git URL dependency pattern in this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is 12+ years old with established publishing history; lack of Sigstore provenance is expected and not a security risk here.	ai	2026/04/24
npm-metadata	url-dep:pako	AI (npm-metadata): Points to official nodeca/pako GitHub repo; long-standing pattern in js-git, not a new or suspicious change.	ai	2026/04/24
npm-metadata	url-dep:git-sha1	AI (npm-metadata): Authored by creationix (same maintainer); long-standing git URL dependency pattern in this package.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): js-git is a well-established legitimate package; 0.0.0 is its genuine initial release from a reputable publisher, not a malicious throwaway.	ai	2026/04/24
semgrep	semgrep:ssh-key-access	AI (semgrep): js-git is a Git client; reading SSH keys in examples/node/ssh.js is expected behavior for SSH transport, not credential theft.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
0.7.8	4 / 0	2017-01-24
0.7.7	4 / 0	2014-08-22
0.7.6	5 / 0	2014-08-05
0.7.5	5 / 0	2014-07-25
0.7.4	5 / 0	2014-07-25
0.7.3	5 / 0	2014-07-19
0.7.2	5 / 0	2014-07-19
0.7.1	5 / 0	2014-07-19
0.6.2	3 / 4	2014-01-09
0.6.1	3 / 4	2013-11-15
0.6.0	3 / 4	2013-11-09
0.5.4	2 / 4	2013-10-23
0.5.3	2 / 4	2013-10-18
0.5.2	2 / 4	2013-10-04
0.5.0	2 / 4	2013-09-25
0.4.2	2 / 4	2013-09-14
0.4.1	2 / 4	2013-09-13
0.4.0	2 / 4	2013-09-12
0.3.3	2 / 3	2013-09-09
0.3.2	1 / 3	2013-09-06
0.3.1	1 / 3	2013-08-29
0.3.0	1 / 3	2013-08-28
0.2.5	3 / 3	2013-08-28
0.2.4	3 / 3	2013-08-28
0.2.3	3 / 2	2013-08-09
0.2.2	3 / 2	2013-08-09
0.2.1	3 / 2	2013-08-09
0.2.0	2 / 3	2013-08-09
0.0.0	1 / 0	2013-07-27

v0.7.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

2 findings

HIGH ssh-key-access: examples/node/ssh.js:25 semgrep

Accessing SSH keys — strong indicator of credential theft 23 | } 24 | else { > 25 | config.privateKey = require('fs').readFileSync(process.env.HOME + "/.ssh/id_rsa"); 26 | } 27 | if (opts.pathname.substr(0, 2) === "/:") opts.pathname = opts.pathname.substr(2);

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.