Add SECURITY.md and Deno workflow for linting and testing - #65
Conversation
Add a security policy document outlining supported versions and vulnerability reporting.
This workflow installs Deno and runs linting and tests on push and pull request events.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eb8de14ff2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: deno lint | ||
|
|
||
| - name: Run tests | ||
| run: deno test -A |
There was a problem hiding this comment.
deno test with the repo's actual test runner
This workflow runs deno test -A, but this repository’s tests are written for Jest (package.json defines "test": "jest", and src/utils/http-client.test.ts uses Jest globals like describe/it/expect). The Deno CLI’s deno test command executes Deno’s built-in runner (tests registered via Deno.test(...)), so this step will fail against the current test suite and leave CI failing on every push/PR to main.
Useful? React with 👍 / 👎.
|
Thanks for the contribution! As of v0.2.0 this package was rewritten from a standalone MCP server into a thin stdio proxy to the unified 21st MCP (https://21st.dev/api/mcp), and the code this PR targets no longer exists. Tool annotations, JSON-RPC handling, and the tools themselves now live server-side. Closing as obsolete - see the new README for the current setup (npx @21st-dev/cli@latest init). |
2 participants
No description provided.