@joggr/cli-linux-x64
Joggr CLI binary for Linux x64
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): markdown.so is a native library component of the Joggr CLI tool, shipped alongside jog binary and ast-grep. No install scripts; binary is simply distributed as a file. Consistent with legitimate CLI binary distribution pattern across all versions. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 0 / 0 | |
| 0.7.2 | 0 / 0 | |
| 0.7.1 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.6.5 | 0 / 0 | |
| 0.6.0 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.2 | 0 / 0 | |
| 0.4.1 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.5 | 0 / 0 | |
| 0.3.4 | 0 / 0 | |
| 0.3.2 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.7.3
2 findingsPackage contains compiled binaries that could be backdoors: • fd • rg • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
2 findingsPackage contains compiled binaries that could be backdoors: • fd • rg • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
2 findingsPackage contains compiled binaries that could be backdoors: • fd • rg • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
2 findingsPackage contains compiled binaries that could be backdoors: • fd • rg • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
2 findingsPackage contains compiled binaries that could be backdoors: • fd • rg • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • markdown.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.