Repository navigation
Open
Labels
taskMaintenance, refactoring, dependency, or tooling workMaintenance, refactoring, dependency, or tooling work
Milestone
Description
Part of #88.
Problem
The repository is private. The DevFrame listing, GitHub Pages for the landing page, free macOS and Windows runners, and npm provenance all need a public repository. Issues and their comments become public with it, including the security review in #94.
State
The repository is public as of 2026-11-17. It went public before the kit redaction items landed, by the owner's call; those items are no longer a gate here and stay first in line in #123.
Done
- License decided: GPL-3.0-only.
@rivus/estela0.2.0 to 0.3.1 released;@rivus/agent-tracedeprecated on npm.
Before changing visibility
- Redaction gaps closed in
@rivus/agent-kitand picked up here ([Task]: agent-kit changes Estela is waiting for #123): titles cut before redaction, pattern coverage, path-boundary matching. Moved: tracked in [Task]: agent-kit changes Estela is waiting for #123, not a gate any more. - The medium findings in [Task]: Security pass with session content as untrusted input #94 fixed:
build --out-dirdeleting an existing directory;--no-authwithout a warning or a guard. Fixed in fix(cli): handle port and host flags and harden untrusted inputs #133. - Audit git history and
fixtures/for secrets and machine paths; attach the result here. Done 2026-11-17, result in the comments: no credentials; two items for the owner. - Repository topics (including
dsh-pluginonly once the plugin exists), social preview image, homepage URL. Topics set on 2026-11-17; the social preview image and the homepage URL (after Pages, [Feature]: Landing page #100) remain.
After
- Enable GitHub Pages and run the landing page workflow ([Feature]: Landing page #100).
- CI on macOS and Windows ([Task]: Run CI on macOS and Windows #92), done in ci: run the unit and smoke suites on macOS and Windows #144;
mainis protected withtestand the fiveplatformschecks required. - Release 0.4.0 (chore(release): version packages #137), the first that can carry npm provenance, and check the attestation on npm. Published 2026-11-17 from d90ca2b after fix(build): restore the web build dependency of @rivus/estela #145 fixed the Publish check; the SLSA provenance names
PerfectPan/estela,publish.ymlonmain. - DevFrame ecosystem submission ([Task]: Submit the project to the DevFrame ecosystem page #106).
Acceptance Criteria
- The audit result is attached; the repository is public; the next release carries npm provenance.
Metadata
Metadata
Assignees
Labels
taskMaintenance, refactoring, dependency, or tooling workMaintenance, refactoring, dependency, or tooling work
Activity
nyx-cell commentedon Nov 12, 2026
License decided: stays GPL-3.0-only.
nyx-cell commentedon Nov 13, 2026
Status:
@rivus/estela0.2.0 and 0.3.0 are published through the Publish workflow with trusted publishing. Still to do before the repository goes public: the redaction items in #123 and the medium findings in #94 (build --out-dirdeleting an existing directory,--no-authwithout a guard), the history audit, repository topics and social preview, andnpm deprecate @rivus/agent-trace.[-][Task]: Make the repository public and release 0.2.0[/-][+][Task]: Make the repository public[/+]PerfectPan commentedon Nov 17, 2026
Git history audit, 2026-11-17
Scope: a mirror clone of this repository with every branch, every tag, and the 91
refs/pull/*refs GitHub serves: 440 commits, 3,437 text blobs (binary blobs skipped), and every commit message. No dedicated scanner was available, so this is a pattern pass over every blob:sk-/sk-ant-/sk_live_keys, AWS key ids and secret keys, GitHub, GitLab, Slack (tokens and webhooks), npm, Hugging Face, and Google API keys, PEM private keys, JWTs, Bearer and Basic values, URL userinfo, secret assignments (PASSWORD=and similar), home paths (/Users/…,/home/…,C:\Users\…), email addresses, and internal host names.Result:
packages/kernel/src/redact.test.ts,apps/e2e/src/e2e/security.e2e.ts, the demo and compaction fixtures);postgres://user:password@hostis the example indocs/guide/privacy.md;/Users/aliceand/Users/alare test inputs for the cut-home workaround inpackages/server/src/agent-tools/.065ae72has a local home directory indocs/VISION.md;maindropped it in chore: adopt the project template workflow #3. Every ref contains the root commit, so removing it means rewriting all history and the release tags, and GitHub keeps therefs/pull/*refs unless GitHub Support purges them. Recommendation: keep it; it names a user directory, not a credential. Owner to decide.main(refactor(repo): rename agent-trace to Estela #107 to feat(e2e): show cost and the context diff in the demo walkthrough #129) carry a personal author and committer email instead of a GitHub noreply address. They are already public; future commits from that account can use its noreply address. Owner to decide.