A lightweight polyfill for Temporal, successor to the JavaScript Date object
78%
Total Score
healthy
Active releases and commits support this package, with a concentrated maintainer base and unpinned workflow actions as the main concerns.
One contributor made 85 of 89 recent commits, or about 96%, creating a meaningful continuity risk; the five active contributors and organization backing partly compensate.
The project uses npm build scripts but reports no security scanning tools, leaving a transparency and maintenance-hygiene gap despite otherwise active development.
No repository security policy is present, which weakens the project's documented process for handling security reports.
The sole workflow was fully analyzed with no injection or high-severity findings, but all 3 action references are unpinned, reducing build reproducibility and update safety.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2024-10016 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. temporal-polyfill is vulnerable to Inefficient Regular Expression Complexity in versions 0.0.0 - 0.2.1. | 0.0.0 - 0.2.1 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
temporal-spec Version 1.0.1 | — | — |
temporal-utils Version 1.0.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.