KudoAI/chatgpt.js
KudoAI/chatgpt.jsClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Action `actions/checkout` pinned to mutable ref `@v6.0.3`: `uses
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `KudoAI/chatgpt.js` **Score: 82/100 (C+)** · 18 findings · scanned 2026-06-05 21:50 UTC · 3,924 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 15 | | MEDIUM | 0 | | LOW | 1 | 📊 [Full filterable report](https://repobility.com/scan/5bdade1a-ab64-4fbd-86a8-36517dfd50bc/) ·  ### Top findings 1. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6.0.3`: `uses `.github/workflows/update-jsd-shields-weekly.yml:17` · ✓ Repobility 2. **HIGH** `MINED115` — Action `actions/setup-node` pinned to mutable ref `@v6.4.0`: `uses `.github/workflows/lint-on-push-pr.yml:11` · ✓ Repobility 3. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6.0.3`: `uses `.github/workflows/lint-on-push-pr.yml:10` · ✓ Repobility 4. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6.0.3`: `uses `.github/workflows/sync-changes-to-js-utils.yml:20` · ✓ Repobility 5. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6.0.3`: `uses `.github/workflows/sync-changes-to-js-utils.yml:16` · ✓ Repobility --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/5bdade1a-ab64-4fbd-86a8-36517dfd50bc/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.