Config-driven data migration between MySQL, PostgreSQL, SQLite and SQL Server: transforms, validation, ID mapping, resume and verify
70%
Total Score
caution
A first release with no recorded commit history and entirely unpinned workflow actions leaves maintenance and build-integrity questions.
The registry namespace and repository owner are the same individual account. A single-person project is plausible here and is consistent with the matching repository evidence, but it provides limited organizational redundancy.
This is the first release, published 0 days ago, so there is no release history to demonstrate sustained maintenance or stability. Its newness explains the gap but does not remove the uncertainty.
No commits or active maintainers were recorded in the last three months. Because the package itself is 0 days old, this mainly reflects insufficient history rather than confirmed abandonment.
No security policy is present. This is a transparency gap for a tool that handles database migrations, though it is not by itself evidence of unsafe maintenance.
Version v0.1.0 is not a stable major release, which indicates an early API and project maturity stage. It is not marked as a prerelease, so the concern is limited to early-version stability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^2.0|^3.0 | — | — |
symfony/yaml Version ^6.4|^7.0|^8.0 | — | — |
symfony/console Version ^6.4|^7.0|^8.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.