← Back to scan
File as GitHub Issue repo: mnaoumov/obsidian-advanced-exclude

Push this scan report to mnaoumov/obsidian-advanced-exclude

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

Parallel implementation file sits beside a canonical file

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
HIGH SEC128 [SEC128] Async function without await — fire-and-forget Promise (AI mistake): Async call … src/file-tree-component.ts:145
HIGH MINED115 Action `actions/attest` pinned to mutable ref `@v4` .github/workflows/attest-release-assets…:22
MED SEC045 [SEC045] eval()/exec() on stored or user-supplied data: eval() and exec() on data — even … scripts/commit.ts:3
MED DEPCUR-NPM npm package `ignore` is 2 major version(s) behind (5.3.2 -> 7.0.5) package.json
MED AIC001 Parallel implementation file sits beside a canonical file scripts/lint-md-fix.ts:1
MED AIC001 Parallel implementation file sits beside a canonical file scripts/lint-fix.ts:1
MED AIC001 Parallel implementation file sits beside a canonical file scripts/build-clean.ts:1
LOW DEPCUR-NPM npm package `obsidian` is minor version(s) behind (1.12.3 -> 1.13.0) package.json
LOW DEPCUR-NPM npm package `jiti` is minor version(s) behind (2.6.1 -> 2.7.0) package.json
INFO MINED044 [MINED044] Js Console Log Prod: console.log left in code. Should be replaced with logger … src/file-tree-component.ts:209
Reset to top 5 10 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `mnaoumov/obsidian-advanced-exclude`

**Score: 87/100 (A)**  ·  10 findings  ·  scanned 2026-06-05 23:54 UTC  ·  5,490 LOC

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

📊 [Full filterable report](https://repobility.com/scan/60fa7b46-01c5-4032-8504-b98a685a59d0/)  ·  ![scorecard](https://repobility.com/scan/60fa7b46-01c5-4032-8504-b98a685a59d0/report.png?v=1780703669-s2)

### Top findings

1. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake)
   `src/file-tree-component.ts:145`
2. **HIGH** `MINED115` — Action `actions/attest` pinned to mutable ref `@v4`
   `.github/workflows/attest-release-assets.yml:22` · ✓ Repobility
3. **MEDIUM** `SEC045` — eval()/exec() on stored or user-supplied data
   `scripts/commit.ts:3` · CWE-95 · A03:2021 Injection
4. **MEDIUM** `DEPCUR-NPM` — npm package `ignore` is 2 major version(s) behind (5.3.2 -> 7.0.5)
   `package.json`
5. **MEDIUM** `AIC001` — Parallel implementation file sits beside a canonical file
   `scripts/lint-md-fix.ts:1`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/60fa7b46-01c5-4032-8504-b98a685a59d0/_
Megaproject â high spam risk
Could not determine 'mnaoumov/obsidian-advanced-exclude' 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.
Open in GitHub to file this issue 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.