git-latest-tag MIT 7 versions

git-latest-tag

npm Repository Homepage

Get the most recent git tag of your repository using git-describe(1)

7

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

stevemao

Keywords

git-latest-tagrecenttaggit-describe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package has been at 0.0.0 for 11+ years from a well-established publisher; this is a legitimate initial version, not a malicious throwaway.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): Package's core purpose is invoking git CLI commands via child_process; this is expected and benign for this package.	ai	2026/04/24
semgrep	semgrep:child-process-exec	AI (semgrep): exec() calls run hardcoded git commands (git describe, git log) — no user-controlled input, no arbitrary command execution risk.	ai	2026/04/24

Versions (showing 7 of 7)

Version	Deps	Published
0.0.6	2 / 3	2015-02-24
0.0.5	2 / 1	2015-02-24
0.0.4	1 / 1	2015-02-23
0.0.3	1 / 1	2015-02-23
0.0.2	1 / 1	2015-02-23
0.0.1	1 / 1	2015-02-23
0.0.0	1 / 1	2015-02-23

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

1 finding

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.