@shmindmaster/repocontext
Advanced tools
@shmindmaster/repocontext - npm Package Compare versions
Package was removed
Sorry, it seems this package was removed from the registry
+8
-0
@@ -5,2 +5,9 @@ # Changelog | ||
| ## [0.2.1] - 2026-07-28 | ||
| ### Fixed | ||
| - Corrected public release, installation, client-configuration, website, and roadmap guidance after the npm launch. | ||
| - Made release verification dispatchable against an existing immutable version tag and fixed its shell quoting. | ||
| ## [0.2.0] - 2026-07-28 | ||
@@ -41,2 +48,3 @@ | ||
| [0.2.1]: https://github.com/shmindmaster/repocontext/releases/tag/v0.2.1 | ||
| [0.2.0]: https://github.com/shmindmaster/repocontext/releases/tag/v0.2.0 |
+1
-1
@@ -17,3 +17,3 @@ #!/usr/bin/env node | ||
| function createServer() { | ||
| const server = new mcp_js_1.McpServer({ name: 'repocontext', version: '0.2.0' }); | ||
| const server = new mcp_js_1.McpServer({ name: 'repocontext', version: '0.2.1' }); | ||
| server.registerTool('wiki.catalog', { | ||
@@ -20,0 +20,0 @@ annotations: READ_ONLY, |
+2
-2
@@ -5,3 +5,3 @@ # CI evidence brief | ||
| After `@shmindmaster/repocontext@0.2.0` is published, this GitHub Actions job checks out one repository, creates its registry under the runner's temporary directory, generates a technical brief for the checked-out commit, and uploads the JSON artifact: | ||
| After `@shmindmaster/repocontext@0.2.1` is published, this GitHub Actions job checks out one repository, creates its registry under the runner's temporary directory, generates a technical brief for the checked-out commit, and uploads the JSON artifact: | ||
@@ -27,3 +27,3 @@ ```yaml | ||
| node-version: 22 | ||
| - run: npm install --global @shmindmaster/repocontext@0.2.0 | ||
| - run: npm install --global @shmindmaster/repocontext@0.2.1 | ||
| - name: Build registry | ||
@@ -30,0 +30,0 @@ shell: bash |
+3
-3
| # MCP client setup | ||
| RepoContext works as a local stdio server in MCP clients that accept a command, arguments, and environment variables. These examples use the source build because the npm package is not public yet. | ||
| RepoContext works as a local stdio server in MCP clients that accept a command, arguments, and environment variables. These examples use a source build; use the public `npx` command below when a local checkout is unnecessary. | ||
@@ -90,3 +90,3 @@ Before configuring a client: | ||
| name: RepoContext | ||
| version: 0.2.0 | ||
| version: 0.2.1 | ||
| schema: v1 | ||
@@ -110,4 +110,4 @@ mcpServers: | ||
| After `@shmindmaster/repocontext@0.2.0` is published and externally verified, replace `command: node` and the compiled path with `command: npx` (`npx.cmd` when a Windows client requires it) and `args: ["-y", "@shmindmaster/repocontext@0.2.0"]`. | ||
| For the public package, replace `command: node` and the compiled path with `command: npx` (`npx.cmd` when a Windows client requires it) and `args: ["-y", "@shmindmaster/repocontext@0.2.1"]`. | ||
| The configuration blocks are syntax-checked by `pnpm verify:clients`. Client-native activation still requires the installed client and, for the `npx` form, the public npm package. |
| # Contributor backlog | ||
| Everything below requires an external dependency, release decision, or additional evidence. These are issue-ready drafts, not claims that the work is complete. | ||
| Everything below requires additional evidence or external infrastructure. These are issue-ready drafts, not claims that the work is complete. | ||
| ## Publish 0.2 and verify public installation | ||
| **Suggested labels:** `release`, `infra`, `help wanted` | ||
| **Problem:** Source and tarball checks pass, but `@shmindmaster/repocontext` is not yet published on npm. The tag workflow cannot authenticate until the package exists and npm trusts `.github/workflows/release.yml`. | ||
| **Why it matters:** The public `npx -y @shmindmaster/repocontext@0.2.0` onboarding path and provenance badge cannot be verified locally. | ||
| **Relevant files:** `package.json`, `.github/workflows/release.yml`, `scripts/verify-package.mjs`, `README.md`. | ||
| **Expected outcome:** A reviewed `v0.2.0` tag publishes through npm OIDC, and clean Node 20, 22, and 24 environments reach `doctor`, a Context Brief, and a first MCP answer without cloning the repository. | ||
| **Acceptance criteria:** | ||
| - Register `shmindmaster/repocontext` and `release.yml` as the npm trusted publisher with `npm publish` permission. | ||
| - Push the reviewed `v0.2.0` tag only after exact-head CI is green. | ||
| - Confirm npm provenance and package metadata. | ||
| - Run `npx -y @shmindmaster/repocontext@0.2.0 doctor` from clean Node 20, 22, and 24 environments. | ||
| - Update README release status only after those checks pass. | ||
| **Proof:** `npm view @shmindmaster/repocontext@0.2.0 --json`, `npx -y @shmindmaster/repocontext@0.2.0 doctor`, and the published workflow run URL. | ||
| ## Deploy the public website with isolated analytics | ||
| **Suggested labels:** `release`, `website`, `analytics`, `help wanted` | ||
| **Problem:** The static website, browser matrix, and manual Pages workflow are merged, and a dedicated RepoContext PostHog project exists. GitHub Pages is not configured, the PostHog project still has IP anonymization and server-side cookieless hashing disabled, and no repository variable connects the site to analytics. | ||
| **Why it matters:** GitHub's short repository-traffic window cannot measure landing-page comprehension or install conversion, while mixing RepoContext into another application's PostHog project would contaminate events and privacy settings. | ||
| **Relevant files:** `site/`, `tests/browser/site.spec.mjs`, `.github/workflows/pages.yml`, `docs/website.md`. | ||
| **Expected outcome:** A public HTTPS site serves the reviewed artifact and sends only anonymous website events to an isolated RepoContext PostHog project. | ||
| **Acceptance criteria:** | ||
| - Configure GitHub Pages to deploy through GitHub Actions and run the manual `Deploy website` workflow. | ||
| - Enable cookieless server hashing and IP anonymization in the dedicated `RepoContext` PostHog project. | ||
| - Keep autocapture and session replay disabled, then set `POSTHOG_REPOCONTEXT_PROJECT_KEY` as a repository variable. | ||
| - Verify `$pageview`, `cta_clicked`, and `audience_changed` contain no repository, filesystem, question, citation, MCP, token, or client-config data. | ||
| - Confirm the production URL in Chromium and rerun the committed browser matrix. | ||
| **Proof:** `pnpm site:test`, the Pages deployment URL, and a PostHog event query grouped by event name with no disallowed properties. | ||
| ## Validate the Context Brief with representative users | ||
@@ -48,0 +6,0 @@ |
+1
-1
| { | ||
| "name": "@shmindmaster/repocontext", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", | ||
| "type": "commonjs", | ||
@@ -5,0 +5,0 @@ "description": "Give coding agents fast, commit-pinned context across the repositories that matter.", |
+3
-4
@@ -18,5 +18,5 @@ # RepoContext | ||
| > **Release status:** RepoContext 0.2 is a release candidate. Its source, tests, build, and packed-package flow are validated, but the npm package has not been published yet. Install from source until the first public package release is announced in this repository. | ||
| > **Release status:** [`@shmindmaster/repocontext`](https://www.npmjs.com/package/@shmindmaster/repocontext) is publicly available on npm. Clean `npx` installs are verified on Node 20, 22, and 24. | ||
| The repository also contains a static product site and a manual GitHub Pages deployment workflow. It remains unpublished until the Pages deployment is explicitly run. Website analytics are optional, cookieless, and isolated to a dedicated RepoContext PostHog project; the CLI and MCP transports contain no telemetry. | ||
| The repository also contains a static product site at [shmindmaster.github.io/repocontext](https://shmindmaster.github.io/repocontext/). Website analytics are optional, cookieless, and isolated to a dedicated RepoContext PostHog project; the CLI and MCP transports contain no telemetry. | ||
@@ -172,3 +172,2 @@ ## Prerequisites | ||
| - The npm package is not published yet; source installation is the supported release-candidate path. | ||
| - Local reads are pinned to the checked-out `HEAD`. Dirty and untracked work is intentionally excluded and may make `doctor` report `attention`. | ||
@@ -178,3 +177,3 @@ - The HTTP transport serves a generated documentation and manifest snapshot, not repository source code or Git history. | ||
| - User registries containing local filesystem paths are excluded from the npm package and remote image. Snapshot builds generate a separate registry containing only image-local paths. | ||
| - Client configuration schemas are verified from current official documentation, but native-client activation and the `npx` form remain publication-time checks. | ||
| - Client configuration schemas are verified from current official documentation; native-client activation remains a local client check. | ||
@@ -181,0 +180,0 @@ ## Development |
+2
-5
@@ -5,3 +5,3 @@ # Roadmap | ||
| ## Completed in the 0.2 release candidate | ||
| ## Completed in the 0.2 release | ||
@@ -16,9 +16,6 @@ - Eight bounded, read-only MCP tools for cross-repository documentation and source evidence. | ||
| - Node 20/22/24 CI and tag-triggered npm trusted-publishing automation. | ||
| - Static public website source with cross-browser regression tests and a manual deployment workflow. | ||
| - Static public website, cookieless analytics, and cross-browser regression tests. | ||
| ## Current priorities | ||
| - Configure npm package ownership and trusted publishing, then publish a reviewed tag only with explicit authorization. | ||
| - Verify installation from a clean machine after the first public package release. | ||
| - Deploy the website after GitHub Pages and the dedicated RepoContext PostHog project's privacy settings are configured. | ||
| - Validate the existing workflow with technical and cross-functional users before expanding the tool contract. | ||
@@ -25,0 +22,0 @@ |
New alerts
Unpublished package
Supply chain riskPackage version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Fixed alerts
Unpublished package
Supply chain riskPackage version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Worsened metrics
- Total package byte prevSize
241584
-1.35%- Number of lines in readme file
211
-0.47%No dependency changes