mrjgreen/db-sync
MIT licensing, tests, a substantial README, and release notes make the package easier to evaluate and maintain locally. Its dependencies are modest, but the long maintenance gap makes adoption a liability for production systems.
44%
Total Score
33
100
81
83
Health Score Breakdown
The last registry release was on April 10, 2017, with no releases in the last 12 months. This long gap is strong evidence that active maintenance has stopped.
The repository had zero commits and zero active maintainers in the last three months, reinforcing the registry evidence of prolonged inactivity.
The package and repository are owned by the same individual account, so there is no organizational backing shown to compensate for the thin current maintenance activity.
There were no new or closed issues or pull requests in the last month, while 9 issues and 2 pull requests remain open. This suggests little current project attention.
Composer is used for builds, which fits the ecosystem, but no security scanning tools are configured. This is a modest transparency gap rather than evidence of abandonment by itself.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^1.0 | — | — |
symfony/debug Version ^3.2 | — | — |
symfony/console Version ^3.2 | — | — |
mrjgreen/database Version ^2.5 | — | — |
ramsey/array_column Version ^1.1 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 12 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.