sandboxed-api
v20241008 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on sandboxed-api's page any more, so we've brought you to the top.
Sandboxed API (SAPI) is an open-source project built on Google's Sandbox2 that makes sandboxingsandboxingRunning code inside a restricted environment that limits what it can access or change. The isolation reduces the impact of mistakes or untrusted code, depending on the sandbox's controls. individual C/C++ libraries less burdensome.
sapi_library(
name = "my_lib_sapi",
generator_version = 2,
functions = ["MyFunc"],
lib = ":my_lib",
lib_name = "MyLib",
namespace = "mylib",
)
What you can do now
Summary
sandboxed-api is an open-source Apache-2.0 C++ framework for isolating individual C/C++ libraries from a host program, aimed at application developers and teams hardening native-code dependencies. It is used as a self-hosted library framework with Bazel, generating interfaces for sandboxed libraries and applying a separate security policy to each one rather than a policy covering the whole application. Its documentation presents it as a layer over Google’s Sandbox2; Sandbox2 is included and can run independently. The Google Sandbox Team maintains it, with commits and releases continuing through 2026.
Sandboxed API (SAPI) is an open-source project built on Google's Sandbox2 that makes sandboxing individual C/C++ libraries less burdensome.
How sandboxed-api helps
Which of my native-code dependencies can execute without directly compromising the host application?
runs the library in a separate Sandbox2 process behind a generated interface, isolating its code from the main program; the boundary protects against code-execution vulnerabilities in that library, but does not make the library itself trustworthy
What access should each library have while handling my application’s data?
applies a separate, tightly defined security policy to each sandboxed library, restricting its syscall and resource footprint rather than combining every dependency’s requirements; the answer depends on the policy configured for that library
How can I reuse the same library sandbox across my C++ applications?
packages the library’s generated interface, data exchange boundary, and Sandbox2 restrictions for reuse, avoiding a fresh sandbox implementation and policy design for each project
Which part of my application is isolated when a vulnerable C/C++ library is called?
isolates the selected library rather than the whole program, so the host application communicates with it through the generated sandbox interface; other application code remains outside that library’s sandbox boundary
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for sandboxed-api, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sandboxed-api puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
1 entry
No entries match these filters.
- October 20241
Project health
Issue, contributor and maintainer activity in google/sandboxed-api, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors not measured distinct committers, last 12 months
- Maintainers not measured core set, last 12 months
- Bus factor not measured committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close 4.2 years issues closed, last 12 months
- Open backlog 21 of 64 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 21
- Contributors / month not measured
- Commits / month not measured
- Stars not measured
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.