git-raw-commits
Get raw git commits out of your repository using git-log(1).
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:child-process-import | AI (semgrep): git-raw-commits uses execFile to invoke git-log(1) — child_process usage is core to the package's documented purpose and stable across all versions. | ai | |
| provenance | publisher-changed | AI (provenance): dangreen is an established publisher (599 approved, 0 rejected) maintaining the conventional-changelog monorepo; transition from oss-bot automation account is legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dangreen is a known, trusted maintainer of the conventional-changelog ecosystem with a strong track record. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.0.0 | 3 / 0 | |
| 3.0.0 | 3 / 0 | |
| 2.0.11 | 5 / 0 | |
| 2.0.10 | 5 / 0 | |
| 2.0.9 | 5 / 0 | |
| 2.0.8 | 5 / 0 | |
| 2.0.7 | 5 / 0 | |
| 2.0.3 | 5 / 0 | |
| 2.0.2 | 5 / 0 | |
| 2.0.0 | 5 / 2 | |
| 1.3.6 | 5 / 2 | |
| 1.3.5 | 5 / 2 | |
| 1.3.4 | 5 / 2 | |
| 1.3.3 | 5 / 7 | |
| 1.3.2 | 5 / 7 | |
| 1.3.1 | 5 / 7 | |
| 1.3.0 | 5 / 7 | |
| 1.2.0 | 5 / 7 | |
| 1.1.2 | 5 / 7 | |
| 1.1.1 | 5 / 7 | |
| 1.1.0 | 5 / 7 | |
| 1.0.0 | 5 / 7 | |
| 0.1.2 | 5 / 7 | |
| 0.1.1 | 5 / 7 | |
| 0.1.0 | 5 / 7 | |
| 0.0.8 | 5 / 7 | |
| 0.0.7 | 5 / 7 | |
| 0.0.6 | 5 / 7 | |
| 0.0.5 | 5 / 5 | |
| 0.0.4 | 5 / 5 | |
| 0.0.3 | 5 / 5 | |
| 0.0.2 | 5 / 6 | |
| 0.0.1 | 5 / 3 | |
| 0.0.0 | 5 / 3 |
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oss-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.