@joggr/cli-linux-arm64
Joggr CLI binary for Linux ARM64
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary packages legitimately have no deps, no keywords, and tiny JS payload — the binary itself is the payload. These signals are structural false positives for this package type. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific CLI binary package; markdown.so is a native ast-grep language plugin, consistent with the package's documented purpose. No install scripts execute it automatically. | ai |
Versions (showing 23 of 23)
| 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.4 | 0 / 0 | |
| 0.6.3 | 0 / 0 | |
| 0.6.2 | 0 / 0 | |
| 0.6.1 | 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.2.1 | 0 / 0 | |
| 0.2.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.4
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.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.6.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.6.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.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.2.1
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: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage 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.