
Research
/Security News
PolinRider Spreads Through Compromised GitHub Accounts and Packagist
Operators behind PolinRider used a compromised GitHub account to plant malware in four development versions of a Packagist package with 700,000+ downloads.
@blacklake-systems/surface-cli
Advanced tools
BlackLake Surface — control layer for AI actions (cloud or local)
⚠️ Deprecated. This package is now part of the unified
blacklakenpm package. Installblacklakeand usenpx blacklake servefor the same local API + dashboard + SQLite. See the migration doc for sed-style search-and-replace examples. This package will continue to ship as a thin re-export through the next two minor versions.
BlackLake — AI control infrastructure and analytics. This package historically shipped the local CLI; it now re-exports through the unified blacklake package.
Surface is the control layer for AI actions. Use the CLI when Codex, Claude, Cursor, CI jobs, backend agents, or shell commands are about to touch real systems and you want the same policy, approval, cost, and signed-receipt model locally.
npx @blacklake-systems/surface-cli
This starts the local Surface API and console, backed by ~/.blacklake/blacklake.db. Local is the fastest private first run; the hosted console is for shared policies, approvals, budgets, exports, and team visibility.
blacklake
blacklake --help
blacklake --version
blacklake mcp
blacklake blx <cmd...>
blacklake demo depth-with-approval
For cloud users, point MCP-compatible tools at the hosted gateway:
{
"mcpServers": {
"blacklake": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.blacklake.systems/mcp",
"--header",
"Authorization: Bearer YOUR_BL_USER_KEY"
]
}
}
}
Register real MCP services in the console first, for example:
cloudflare-docsengineering-github-repositoriesproduct-linear-workspacecompany-notion-workspacejira-confluence-workspaceFor local users, run blacklake mcp as a stdio bridge from your MCP client and put upstream MCP services in ~/.blacklake/mcp-config.json.
Use blx when an AI-assisted shell workflow is about to run a consequential command:
blacklake blx git push origin main
blacklake blx gh pr merge 123 --squash
blacklake blx gcloud run deploy api
blacklake blx terraform apply
blacklake blx kubectl apply -f deploy.yaml
Read-only/build commands are allowed through. Write/deploy/destructive commands are classified and governed before execution.
blacklake demo depth-with-approval
Creates a small Depth workflow that pauses on a Surface approval.
BlackLake controls the paths you route through it: MCP gateway, SDK, GitHub Action, blx, cloud audit ingest, and Depth workflows. It does not invisibly intercept every process on the machine or replace cloud IAM.
FAQs
BlackLake Surface — control layer for AI actions (cloud or local)
The npm package @blacklake-systems/surface-cli receives a total of 0 weekly downloads. As such, @blacklake-systems/surface-cli popularity was classified as not popular.
We found that @blacklake-systems/surface-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Research
/Security News
Operators behind PolinRider used a compromised GitHub account to plant malware in four development versions of a Packagist package with 700,000+ downloads.

Security News
GitHub Actions now supports cache-mode, a least-privilege control on the Actions cache aimed at the cache poisoning technique behind recent compromises.

Company News
Allow myself to introduce... myself.