@blackwell-systems/agent-lsp-darwin-x64
agent-lsp binary for macOS x64 (Intel)
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 binary distribution package; shipping a compiled binary is the entire purpose of this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 0 / 0 | |
| 0.11.2 | 0 / 0 | |
| 0.11.1 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.0 | 0 / 0 | |
| 0.5.4 | 0 / 0 | |
| 0.5.3 | 0 / 0 | |
| 0.5.2 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.3 | 0 / 0 | |
| 0.2.2 | 0 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.2 | 0 / 0 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
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: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
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: • bin/agent-lsp
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: • bin/agent-lsp
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: • bin/agent-lsp
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: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage contains compiled binaries that could be backdoors: • bin/agent-lsp
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.