@inboxapi/cli-darwin-x64
InboxAPI CLI binary for macOS 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): Platform-specific CLI binary package; bundling the binary is its explicit purpose. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.3.16 | 0 / 0 | |
| 0.3.15 | 0 / 0 | |
| 0.3.14 | 0 / 0 | |
| 0.3.13 | 0 / 0 | |
| 0.3.12 | 0 / 0 | |
| 0.3.11 | 0 / 0 | |
| 0.3.10 | 0 / 0 | |
| 0.3.9 | 0 / 0 | |
| 0.3.8 | 0 / 0 | |
| 0.3.7 | 0 / 0 | |
| 0.3.6 | 0 / 0 | |
| 0.3.5 | 0 / 0 | |
| 0.3.4 | 0 / 0 | |
| 0.3.3 | 0 / 0 | |
| 0.3.2 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.25 | 0 / 0 | |
| 0.2.24 | 0 / 0 | |
| 0.2.23 | 0 / 0 | |
| 0.2.22 | 0 / 0 | |
| 0.2.21 | 0 / 0 | |
| 0.2.20 | 0 / 0 | |
| 0.2.19 | 0 / 0 | |
| 0.2.18 | 0 / 0 | |
| 0.2.17 | 0 / 0 | |
| 0.2.16 | 0 / 0 | |
| 0.2.15 | 0 / 0 | |
| 0.2.14 | 0 / 0 | |
| 0.2.13 | 0 / 0 | |
| 0.2.12 | 0 / 0 | |
| 0.2.11 | 0 / 0 | |
| 0.2.10 | 0 / 0 | |
| 0.2.9 | 0 / 0 | |
| 0.2.8 | 0 / 0 | |
| 0.2.7 | 0 / 0 | |
| 0.2.6 | 0 / 0 | |
| 0.2.5 | 0 / 0 | |
| 0.2.4 | 0 / 0 | |
| 0.2.3 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.9 | 0 / 0 | |
| 0.1.8 | 0 / 0 | |
| 0.1.7 | 0 / 0 | |
| 0.1.6 | 0 / 0 | |
| 0.1.5 | 0 / 0 | |
| 0.1.4 | 0 / 0 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.3.16
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
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: • inboxapi-cli
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: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.22
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
2 findingsPackage contains compiled binaries that could be backdoors: • inboxapi-cli
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.