Fix High CVE Vulnerability in Dependencies

[Josephat-S]

What to build

Socket detected 6 instances of a high-severity CVE in 1 package. This is likely coming from tiged or one of its transitive dependencies. We need to identify the vulnerable package, check if a patched version exists, and either upgrade or replace it.

Steps to resolve

1. Run npm audit to identify which package has the CVE.
2. Check if the vulnerability is in tiged itself or a transitive dependency.
3. If a patch exists: upgrade the dependency.
4. If no patch exists: evaluate replacing tiged with degit or a custom GitHub download using tar + fetch.

Acceptance criteria

• npm audit shows 0 high/critical vulnerabilities.
• If tiged is the source, evaluate alternatives (degit, direct GitHub tarball download).
• Document the decision in a comment on this issue.

[meekness12]

I am claiming this task.

[Josephat-S]

I am claiming this task.

You can work on it @meekness12

[Josephat-S]

Resolved by PR #83 (tiged → giget replacement). npm audit now shows 0 vulnerabilities.