Lightspark JS SDK
82%
Total Score
healthy
Healthy — recent releases, active contributors, and organization backing outweigh limited security and workflow hygiene gaps.
Two of three publishing accounts use the lightspark.com domain, but coreymartin uses a gmail.com account. With clear organization backing this is mainly account hygiene, though the outside consumer account is a minor concern.
The project uses build tooling, but no security-scanning tools were detected. This leaves a modest transparency gap in its maintenance controls.
The repository has no documented security policy. For an SDK handling authentication tokens and financial API operations, that weakens vulnerability-reporting transparency.
All seven workflows were analyzed with no untrusted checkouts or script-injection findings. The audit did identify high-confidence template-injection hygiene findings and a low-confidence-impact adhoc package install, while six of 35 action references are unpinned; these do not by themselves indicate a severe dependency risk.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2025-10661 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. @lightsparkdev/lightspark-sdk is vulnerable to Observable Timing Discrepancy in versions 1.0.6 - 1.9.11. | 1.0.6 - 1.9.11 | Low |
| Dependency | Last Release | Score |
|---|---|---|
ws Version ^8.12.1 | — | — |
dayjs Version ^1.11.7 | — | — |
dotenv Version ^16.3.1 | — | — |
graphql Version ^16.6.0 | — | — |
graphql-ws Version ^5.11.3 | — | — |
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.