Repository navigation
Conversation
Anthropic's OSS Scanner builds .oss-scanner/Dockerfile with network access and then audits offline. The image installs the pinned 1.91.0 toolchain, fetches every locked crate for the Runtime workspace, the capsule workspaces and the helper tools, and builds the Runtime and every capsule with test binaries in the dev profile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scanner reads .oss-scanner/threat_model.md before it starts. It names the attacker positions, the Runtime, gateway, capability, isolation, key and Carrier code that matter most, how to run tests and a Runtime offline in the scanner image, the severity scale, and the known SECURITY.md findings to leave alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An offline run of the scanner build steps showed that disk-reserve guards and permission-based failure injection fail on a nearly full volume or as root. Tell the scanner these are environment results. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Anthropic's OSS Scanner sends reports to a primary contact that the project's SECURITY.md lists. Add the shared security address next to GitHub Security Advisories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
develop lists a whole-object Carrier fetch finding, a fixed Carrier request read, and the current isolation boundary: Home holds every App capability, Components share the Runtime process, providers run with the Runtime user's rights, and keys sit next to their data. Tell the scanner these are known, and use develop's free-space error wording. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
andersalm
requested changes
Oct 21, 2026
andersalm
left a comment
Contributor
There was a problem hiding this comment.
Reviewed head 4b8fee69e (cross-family Codex review). One change before merge:
- In
.oss-scanner/threat_model.md, please remove the paragraph that starts "The temporary Mac operator model route…" (around line 230). Under the SECURITY.md rule (#442), public files don't carry that kind of detail; it stays in private tracking.
Everything else checks out:
- The Dockerfile installs Rust 1.91.0, which matches
rust-toolchain.toml. - No credentials and no
curl | sh. - Nothing in CI or the pre-push gate runs it.
- The SECURITY.md reporting line stays consistent with the rest of the file.
The PR merges cleanly with the 0.8.0 train (release/train-0.8.0-rc10). Before merge, please also confirm that security@ela.city exists and who reads it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds the files that Anthropic's OSS Scanner reads from this repository.
.oss-scanner/Dockerfilebuilds the scanner image. The scanner builds it with network access and then works offline. The image installs the toolchain thatrust-toolchain.tomlpins and fetches every crate in every lockfile. It then builds the Runtime workspace and each capsule workspace, with their test binaries, in the dev profile..oss-scanner/threat_model.mdtells the scanner what ElastOS does and where untrusted input enters. It also says which components matter most, how to run the tests and a local Runtime in the image, how we rate severity, and which limitsSECURITY.mdalready lists.SECURITY.mdaddssecurity@ela.cityas a private reporting address, next to GitHub Security Advisories.Generated by Claude Code