Rename exospherehost → failproofai across repo (URLs, X handle, policy namespace)#370
Merged
Merged
Conversation
GitHub org was renamed. Replaces github.com/exospherehost/failproofai with github.com/failproofai/failproofai across package.json metadata, README and 14 translated README badges, CONTRIBUTING, in-app banners (bin/, scripts/, components/), Mintlify docs.json, and 30 translated docs (package-aliases issues link + examples repo-tree link). Also updates the X social handle in docs.json from x.com/exospherehost to x.com/failproofai. LICENSE, package.json author legal entity, contact email, and historical CHANGELOG entries are intentionally left untouched (per audit decisions). https://claude.ai/code/session_01KtaM2jJWogYSpNzp7ziMEa
No asset named exospheresmall exists in public/, app/, or components/ — the matcher exemption was a leftover from the old org's branding. Removing it has no behavioral impact since the path doesn't exist. https://claude.ai/code/session_01KtaM2jJWogYSpNzp7ziMEa
BREAKING CHANGE: Default policy namespace for builtins is now `failproofai`.
User configs that explicitly reference builtins as `exospherehost/<name>`
must update to `failproofai/<name>`. Flat-name shorthand (e.g.
`"sanitize-jwt"`) continues to work unchanged because `normalizePolicyName`
auto-prepends the new default namespace.
Includes:
- src/hooks/policy-registry.ts: one-line constant change (the API surface)
- src/hooks/policy-evaluator.ts + builtin-policies.ts: JSDoc/comment refresh
- 48 test assertions across __tests__/hooks/{policy-registry,policy-evaluator,builtin-policies}.test.ts
- docs/built-in-policies.mdx + 14 translations: 3 namespace mentions each
- package.json: bump 0.0.11-beta.0 → 0.0.11-beta.1
- CHANGELOG.md: new 0.0.11-beta.1 section covering all three commits in
this PR (URL rename, matcher cleanup, namespace rename)
https://claude.ai/code/session_01KtaM2jJWogYSpNzp7ziMEa
📝 WalkthroughWalkthroughThis PR renames the default policy namespace from ChangesOrganization and Policy Namespace Rename
🎯 3 (Moderate) | ⏱️ ~20 minutes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
components/reach-developers.tsx (1)
8-15: ⚡ Quick winUse
GITHUB_REPOfor the “Star us on GitHub” entry too.Line 15 re-hardcodes the same repo URL defined at Line 8, which can drift in future renames.
♻️ Proposed fix
const options = [ { label: "Star us on GitHub", icon: Star, - href: "https://github.com/failproofai/failproofai", + href: GITHUB_REPO, },🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@components/reach-developers.tsx` around lines 8 - 15, Replace the hardcoded repo URL inside the options array with the GITHUB_REPO constant: update the "Star us on GitHub" entry in the options array (the object with label "Star us on GitHub" and icon Star) to use GITHUB_REPO instead of the literal "https://github.com/failproofai/failproofai" so the component consistently references the single source of truth.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 3: CI is failing due to a cross-package version mismatch: the root
package.json version is "0.0.11-beta.1" but some packages/*/package.json files
have a different version; update all packages' "version" fields to
"0.0.11-beta.1" (or alternatively modify the version-check job that compares
PKG_VERSION to ROOT_VERSION) so that the version-check job no longer reports
"Version mismatch"; target files are the "version" field entries in each
packages/*/package.json.
---
Nitpick comments:
In `@components/reach-developers.tsx`:
- Around line 8-15: Replace the hardcoded repo URL inside the options array with
the GITHUB_REPO constant: update the "Star us on GitHub" entry in the options
array (the object with label "Star us on GitHub" and icon Star) to use
GITHUB_REPO instead of the literal "https://github.com/failproofai/failproofai"
so the component consistently references the single source of truth.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f93d8d2e-8806-4c38-8961-1f2412eb8c3e
📒 Files selected for processing (76)
CHANGELOG.mdCONTRIBUTING.mdREADME.md__tests__/components/reach-developers.test.tsx__tests__/hooks/builtin-policies.test.ts__tests__/hooks/policy-evaluator.test.ts__tests__/hooks/policy-registry.test.tsbin/failproofai.mjscomponents/navbar.tsxcomponents/reach-developers.tsxdocs/ar/built-in-policies.mdxdocs/ar/examples.mdxdocs/ar/package-aliases.mdxdocs/built-in-policies.mdxdocs/de/built-in-policies.mdxdocs/de/examples.mdxdocs/de/package-aliases.mdxdocs/docs.jsondocs/es/built-in-policies.mdxdocs/es/examples.mdxdocs/es/package-aliases.mdxdocs/examples.mdxdocs/fr/built-in-policies.mdxdocs/fr/examples.mdxdocs/fr/package-aliases.mdxdocs/he/built-in-policies.mdxdocs/he/examples.mdxdocs/he/package-aliases.mdxdocs/hi/built-in-policies.mdxdocs/hi/examples.mdxdocs/hi/package-aliases.mdxdocs/i18n/README.ar.mddocs/i18n/README.de.mddocs/i18n/README.es.mddocs/i18n/README.fr.mddocs/i18n/README.he.mddocs/i18n/README.hi.mddocs/i18n/README.it.mddocs/i18n/README.ja.mddocs/i18n/README.ko.mddocs/i18n/README.pt-br.mddocs/i18n/README.ru.mddocs/i18n/README.tr.mddocs/i18n/README.vi.mddocs/i18n/README.zh.mddocs/it/built-in-policies.mdxdocs/it/examples.mdxdocs/it/package-aliases.mdxdocs/ja/built-in-policies.mdxdocs/ja/examples.mdxdocs/ja/package-aliases.mdxdocs/ko/built-in-policies.mdxdocs/ko/examples.mdxdocs/ko/package-aliases.mdxdocs/package-aliases.mdxdocs/pt-br/built-in-policies.mdxdocs/pt-br/examples.mdxdocs/pt-br/package-aliases.mdxdocs/ru/built-in-policies.mdxdocs/ru/examples.mdxdocs/ru/package-aliases.mdxdocs/tr/built-in-policies.mdxdocs/tr/examples.mdxdocs/tr/package-aliases.mdxdocs/vi/built-in-policies.mdxdocs/vi/examples.mdxdocs/vi/package-aliases.mdxdocs/zh/built-in-policies.mdxdocs/zh/examples.mdxdocs/zh/package-aliases.mdxpackage.jsonproxy.tsscripts/launch.tssrc/hooks/builtin-policies.tssrc/hooks/policy-evaluator.tssrc/hooks/policy-registry.ts
| { | ||
| "name": "failproofai", | ||
| "version": "0.0.11-beta.0", | ||
| "version": "0.0.11-beta.1", |
There was a problem hiding this comment.
Version bump is currently CI-blocked by cross-package mismatch.
Pipeline is already reporting Version mismatch: $pkg has $PKG_VERSION, expected $ROOT_VERSION. Please sync packages/*/package.json versions to 0.0.11-beta.1 (or adjust the version-check job) before merge.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 3, CI is failing due to a cross-package version
mismatch: the root package.json version is "0.0.11-beta.1" but some
packages/*/package.json files have a different version; update all packages'
"version" fields to "0.0.11-beta.1" (or alternatively modify the version-check
job that compares PKG_VERSION to ROOT_VERSION) so that the version-check job no
longer reports "Version mismatch"; target files are the "version" field entries
in each packages/*/package.json.
4 tasks
NiveditJain
added a commit
that referenced
this pull request
May 20, 2026
npm provenance verification compares package.json repository/homepage/bugs
URLs byte-for-byte against the ${{ github.repository }} value GitHub stamps
into the sigstore attestation. The org rename in #370 lowercased these to
"failproofai/failproofai", which broke publish for 0.0.11-beta.1 with
"422 Error verifying sigstore provenance bundle: Failed to validate
repository information".
GitHub URL routing is case-insensitive, so this only affected provenance
verification, not link resolution.
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
2 participants
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.
Summary
GitHub org was renamed
exospherehost→failproofai. This PR updates therepo to match in 3 focused commits:
a0727c8— URL & handle rename (mechanical, 53 files):package.jsonmetadata (
homepage,repository,bugs), README CI badge (EN + 14translated READMEs),
CONTRIBUTING.md, in-app "Star us" banners(
bin/failproofai.mjs,scripts/launch.ts),components/navbar.tsx,components/reach-developers.tsx(+ test), Mintlifydocs/docs.json(GitHub anchor + footer + X handle
x.com/exospherehost→x.com/failproofai), and 30 translated docs (package-aliases.mdxissues link +
examples.mdxrepo-tree link).b2b38c3— proxy matcher cleanup (1 file): removes the orphanexospheresmalltoken fromproxy.ts's Next.js matcher exemption —no asset by that name exists anywhere in the repo.
bb06ccc—DEFAULT_POLICY_NAMESPACEhard rename (BREAKING, 23 files):one-line constant change in
src/hooks/policy-registry.ts, plus 48 testassertions across 3 test files, JSDoc/comment refresh in
policy-evaluator.tsbuiltin-policies.ts, 15 built-in-policies docs (EN + 14 translations),package.jsonversion bump0.0.11-beta.0→0.0.11-beta.1, and a new## 0.0.11-beta.1 — 2026-05-20CHANGELOG section covering all threecommits (Breaking + Docs + Fixes subsections).
Breaking change
Users whose config explicitly references builtins as
exospherehost/<name>(e.g."enabledPolicies": ["exospherehost/sanitize-jwt"])must update to
failproofai/<name>. Flat-name shorthand(
"sanitize-jwt") continues to work unchanged becausenormalizePolicyName()auto-prepends the new default namespace. Pre-1.0semver permits the break.
Intentionally NOT touched
LICENSE(copyright + Licensor line) — legal entityExosphereHost Inc.unchanged; only the GitHub handle moved.
package.jsonauthorfield — same reasoning.failproofai@exosphere.hostcontact email — domain still owns the mailbox.CHANGELOG.mdentries that mention the old org — historystays factual.
External follow-ups (not code work)
x.com/failproofaiactually exists (was the X handle renamed too?).If not, revert the one-line change in
docs/docs.json:994.npm publish --provenanceon the next publish — no manual npm settingsedit needed.
survive an org rename but worth a quick audit.
Test plan
bun run lint(clean — 1 pre-existing warning, unrelated)bunx tsc --noEmit(clean)bun run test:run— 1623/1623 pass, including all 48 renamednamespace assertions and the 2
reach-developers.test.tsxURL assertionsbun run build(Next.js + dist/cli.mjs + dist/index.js, all green)bun run test:e2e— 290/298 pass; 2 failures (copilot-integration,cursor-integration) reproduce onorigin/main's test files and are asandbox signing-server limitation in the remote dev environment, not a
regression. CI runs in a different environment that doesn't hit this.
exospherehosthits outsideCHANGELOG.mdhttps://github.com/failproofai/failproofai, reach-developers dropdownlinks → same
https://claude.ai/code/session_01KtaM2jJWogYSpNzp7ziMEa
Generated by Claude Code
Summary by CodeRabbit
Breaking Changes
Documentation
Bug Fixes
Chores