Skip to content

[Task]: Make the repository public #90

Open

Description

@nyx-cell

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/estela 0.2.0 to 0.3.1 released; @rivus/agent-trace deprecated on npm.

Before changing visibility

After

Acceptance Criteria

  • The audit result is attached; the repository is public; the next release carries npm provenance.

Activity

  1. added this to the v1.0.0 milestone on Nov 12, 2026
  2. added
    taskMaintenance, refactoring, dependency, or tooling work
    on Nov 12, 2026
  3. nyx-cell commented on Nov 12, 2026

    @nyx-cell
    CollaboratorAuthor

    License decided: stays GPL-3.0-only.

  4. nyx-cell commented on Nov 13, 2026

    @nyx-cell
    CollaboratorAuthor

    Status: @rivus/estela 0.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-dir deleting an existing directory, --no-auth without a guard), the history audit, repository topics and social preview, and npm deprecate @rivus/agent-trace.

  5. changed the title [-][Task]: Make the repository public and release 0.2.0[/-] [+][Task]: Make the repository public[/+] on Nov 13, 2026
  6. PerfectPan commented on Nov 17, 2026

    @PerfectPan
    Owner

    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:

    • No credentials. The token-shaped hits are fake test values (packages/kernel/src/redact.test.ts, apps/e2e/src/e2e/security.e2e.ts, the demo and compaction fixtures); postgres://user:password@host is the example in docs/guide/privacy.md; /Users/alice and /Users/al are test inputs for the cut-home workaround in packages/server/src/agent-tools/.
    • One machine path: the root commit 065ae72 has a local home directory in docs/VISION.md; main dropped 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 the refs/pull/* refs unless GitHub Support purges them. Recommendation: keep it; it names a user directory, not a credential. Owner to decide.
    • Commit metadata: 13 commits on 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    taskMaintenance, refactoring, dependency, or tooling work

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions