Add CI and repo security settings before going public
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, typescript
Research direction
Start by reviewing the repository scripts behind npm test and npm run check, then inspect the existing repository settings and the proposed .github/ additions. Add the pull-request and main-push workflow, branch protection, security scanning, Dependabot configuration, and SECURITY.md with a disclosure contact. Done means the checks run successfully and the requested public-repository protections are configured.
Written by the indexing model from the issue text.
Description
Summary
There is no .github/ directory. npm test and npm run check never run on a pull request, and main has no branch protection.
For a project whose entire value proposition is "this is the safe way to let an agent touch your Meetup account", landing changes with no automated gate is the wrong signal to prospective users.
Suggested additions
- A workflow running
npm ci,npm run checkandnpm teston pull requests and on pushes tomain - Branch protection on
mainrequiring that workflow to pass - CodeQL, or at minimum GitHub's secret scanning and push protection, both free on public repos
- Dependabot for the three runtime dependencies
- A
SECURITY.mdwith a disclosure contact
Note
Dependency hygiene is already good and worth preserving: all dependencies are pinned to exact versions and npm audit reports zero advisories.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SSWConsulting/SSW.MeetupMCP
-
Area: Backend Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Area: Backend Type: Refactor
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Area: Backend Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
Type: Bug Type: DevOps
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Area: Backend Type: Bug
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in SSWConsulting/SSW.MeetupMCP
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vercel-labs/just-bash#464 ·
-
looksLikeSlug() is ASCII-only, so non-Latin entity slugs (e.g. Korean) skip exact match and collapse Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TanStack/tanstack.com#1293 ·