publishr
A tool for harmonious publishing of git and npm packages.
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is `cd lib || npm run build` — a safe no-op that only builds if lib/ is absent. No remote code execution or dangerous behavior. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): publishr is a git/npm publishing tool; child_process usage in git.js is core functionality for shelling out to git commands. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 7 / 16 | |
| 0.0.24 | 7 / 13 | |
| 0.0.23 | 7 / 13 | |
| 0.0.22 | 7 / 13 | |
| 0.0.21 | 6 / 13 | |
| 0.0.20 | 3 / 15 | |
| 0.0.19 | 3 / 13 | |
| 0.0.18 | 3 / 14 | |
| 0.0.16 | 2 / 7 | |
| 0.0.15 | 1 / 8 | |
| 0.0.14 | 1 / 8 | |
| 0.0.13 | 1 / 8 | |
| 0.0.11 | 1 / 4 | |
| 0.0.10 | 1 / 4 | |
| 0.0.9 | 1 / 4 | |
| 0.0.8 | 1 / 4 | |
| 0.0.7 | 1 / 4 | |
| 0.0.6 | 1 / 4 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
2 findingsScript: cd lib || npm run build
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
2 findingsScript: cd lib || npm run build
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.