Strong documentation, typings, release provenance, and active organization backing support adoption. Tighten GitHub App permissions and verify the repository linkage before relying on this release in a sensitive build pipeline.
74%
Total Score
90
94
67
100
All 23 workflows were analyzed, use read-only permissions, and pin all 166 action references. However, a high-confidence high-severity github-app finding reports blanket installation permissions in release.yml, and secrets-inherit findings widen credential exposure; these are material workflow hygiene risks.
Five of seven publishing accounts use the scalar.com domain and the package is organization-backed, but hwkr (hwkr.me) and hanspagel (hanspagel.com) are outside-domain accounts, creating a small account-hygiene concern rather than a maintenance-capacity concern.
The repository name does not match the package name and its README does not mention @scalar/json-magic, so the package-to-repository relationship is not directly established by this signal.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
yaml Version ^2.9.0 | — | — |
pathe Version ^2.0.3 | — | — |
undici Version 7.29.1 | — | — |
@scalar/helpers Version 0.16.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.