A lightweight polyfill for Temporal, successor to the JavaScript Date object
88%
Total Score
80
100
94
80
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable despite the package's otherwise strong maintenance evidence.
The registry lists one publishing account, which is a modest publishing bus factor; the organization-backed repository and active contributor set provide some compensation.
One contributor made 252 of 256 recent commits, creating substantial concentration risk; the organization-owned repository and four additional active contributors provide limited compensation.
The repository uses npm build scripts but reports no security-scanning tools, leaving security hygiene less robust than its maintenance activity.
The repository has no security policy, so vulnerability-reporting and response expectations are not documented.
| 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.