Repository navigation
website: bring Sentinel status up to date with pkg-registry - #101
Merged
Merged
Conversation
The Sentinel page and homepage pillar still said 'auditing proxy live, policy & permissions next' — the pkg-registry repo has since shipped the whole layer (phases through 25): signed policy with lint + dry-run preview, control-plane role tokens, a deny-by-default sandbox (writes and $HOME reads), sentinel explain remediation, identity and release-anomaly signals, durable SQLite observability, and a hardened network trust boundary. Current work there is OSS launch prep. Sourced from pkg-registry's CLAUDE.md phase log and README as of 2026-07-09.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the website copy for Sentinel to reflect its current state (full security layer shipped) as tracked in the pkg-registry repo, removing wedge-stage roadmap language and expanding the feature bullets/status narrative accordingly.
Changes:
- Updated Sentinel status badge/meta lines to “full security layer built · open-source launch prep”.
- Expanded “How it works” bullets on the Sentinel page to reflect the deny-by-default sandbox posture, policy gate capabilities, and additional signals/observability/trust-boundary items.
- Rewrote the Sentinel status paragraph to the “wedge → full layer” framing with a July 2026 timestamp.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| website/src/pages/sentinel.astro | Refreshes Sentinel page status line, feature bullets, and status paragraph to match current shipped capabilities. |
| website/src/pages/index.astro | Updates the Sentinel homepage pillar copy and meta/status line to match the refreshed Sentinel positioning. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Why
The Sentinel page and the homepage pillar still described the project as it was at the wedge stage — "auditing proxy live · policy & permissions next". The pkg-registry repo has since shipped the entire layer (phases through 25) and its current work is OSS launch prep, so the site undersold the project and stated a stale roadmap.
What
Copy-only changes to
website/src/pages/sentinel.astroand the Sentinel pillar inindex.astro, sourced from pkg-registry's CLAUDE.md phase log and README as of 2026-07-09:sentinel explainremediation (advisory-only)Verified with
npm run build— all 4 pages generate cleanly. The demo transcript on the page was checked againstnpm run demooutput in the pkg-registry README and left unchanged (still accurate).