Abstraction over common javascript date management libraries
62%
Total Score
50
100
88
50
Only one registry account has publish access. The linked repository is user-owned rather than organization-owned, so this represents a real bus-factor concern, although repository activity and historical releases provide some compensation.
The package has 52 releases and historically released about every 18 days, but its latest release was about 18 months ago and there were no releases in the last 12 months. The long recent pause lowers confidence in ongoing maintenance.
There were no commits from any active maintainer in the last three months, consistent with the extended release pause and increasing abandonment risk.
There were no new or closed issues and no merged pull requests in the last month, while 19 issues and 15 pull requests remain open. This suggests limited current response capacity.
The repository uses npm scripts, Rollup, and TypeScript, showing a defined build process, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@date-io/core Version ^3.2.0 | — | — |
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.