← Back to scan
File as GitHub Issue repo: JuliaRegistries/General

Push this scan report to JuliaRegistries/General

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Workflow uses `secrets.TAGBOT_TOKEN` on a `pull_request` trigger

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT MINED116 [MINED116] Workflow uses `secrets.ZULIP_API_KEY` on a `pull_request` trigger: This workfl… .github/workflows/breaking_change_feed.…:36
CRIT MINED116 [MINED116] Workflow uses `secrets.ZULIP_API_KEY` on a `pull_request` trigger: This workfl… .github/workflows/feed.yml:80
CRIT MINED116 [MINED116] Workflow uses `secrets.JULIALANGSLACKENDPOINT` on a `pull_request` trigger: Th… .github/workflows/feed.yml:48
CRIT MINED116 [MINED116] Workflow uses `secrets.TAGBOT_TOKEN` on a `pull_request` trigger: This workflo… .github/workflows/TagBotTriggers.yml:35
CRIT MINED116 [MINED116] Workflow uses `secrets.TAGBOT_TOKEN` on a `pull_request` trigger: This workflo… .github/workflows/automerge.yml:234
HIGH SEC040 [SEC040] innerHTML XSS — template literal with server-supplied data: Setting .innerHTML w… .ci/generate_redirects.jl:129
HIGH MINED004 [MINED004] Weak Crypto: MD5/SHA1/DES/RC4 used for security context (not just checksums). .ci/Treecheck/Treecheck.jl:140
HIGH MINED002 [MINED002] Dart Null Bang: value! throws on null. Use ?. or null check. .ci/Treecheck/Treecheck.jl:64
INFO MINED045 [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - TypeError … .ci/Treecheck/Treecheck.jl:64
Reset to top 5 9 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `JuliaRegistries/General`

**Score: 75/100 (B)**  ·  9 findings  ·  scanned 2026-06-05 14:59 UTC  ·  0 LOC

| Severity | Count |
|---|---|
| CRITICAL | 5 |
| HIGH | 3 |
| MEDIUM | 0 |
| LOW | 0 |

📊 [Full filterable report](https://repobility.com/scan/34c06da4-49bc-4358-9c01-80d2ab462c0a/)  ·  ![scorecard](https://repobility.com/scan/34c06da4-49bc-4358-9c01-80d2ab462c0a/report.png?v=1780671576-s2)

### Top findings

1. **CRITICAL** `MINED116` — Workflow uses `secrets.ZULIP_API_KEY` on a `pull_request` trigger
   `.github/workflows/breaking_change_feed.yml:36` · ✓ Repobility
2. **CRITICAL** `MINED116` — Workflow uses `secrets.ZULIP_API_KEY` on a `pull_request` trigger
   `.github/workflows/feed.yml:80` · ✓ Repobility
3. **CRITICAL** `MINED116` — Workflow uses `secrets.JULIALANGSLACKENDPOINT` on a `pull_request` trigger
   `.github/workflows/feed.yml:48` · ✓ Repobility
4. **CRITICAL** `MINED116` — Workflow uses `secrets.TAGBOT_TOKEN` on a `pull_request` trigger
   `.github/workflows/TagBotTriggers.yml:35` · ✓ Repobility
5. **CRITICAL** `MINED116` — Workflow uses `secrets.TAGBOT_TOKEN` on a `pull_request` trigger
   `.github/workflows/automerge.yml:234` · ✓ Repobility

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/34c06da4-49bc-4358-9c01-80d2ab462c0a/_
Megaproject â high spam risk
Could not determine 'JuliaRegistries/General' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Already filed
5/11 findings (45%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.
I read the warnings â override Cancel

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.