A render engine for Node and the browser
87%
Total Score
83
100
94
67
100
The leading contributor made about 60% of recent commits, which is concentrated, but 17 contributors were active and a second contributor supplied 25%. The concentration is a mild resilience concern, not a severe abandonment signal.
The project uses established build and test tools, but no security-scanning tools were detected. That is a modest transparency and hygiene gap.
No security policy was found in the repository. This weakens the project's documented vulnerability-reporting process, though it is not evidence of unsafe code by itself.
All three workflows were analyzed and had no untrusted checkouts or script-injection findings, but all 19 action references are unpinned and the release workflow installs packages outside a lockfile. These are concrete build-reproducibility and supply-chain hygiene weaknesses.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
abs-svg-path Version ^0.1.1 | — | — |
color-string Version ^2.1.4 | — | — |
@babel/runtime Version ^7.20.13 | — | — |
@react-pdf/fns Version 3.1.3 | — | — |
parse-svg-path Version ^0.1.2 | — | — |
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.