mammutgroup/database
Tests, documentation, licensing, and an organization-backed repository provide a usable foundation. No recent releases or commits, plus no security policy or scanning, make long-term compatibility and maintenance uncertain.
35%
Total Score
50
75
75
Health Score Breakdown
The latest release was in July 2017, with no releases in the last 12 months across a package age of about 9 years. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The repository has one star and no forks, offering little community evidence or backup capacity. Low popularity alone is not decisive, but it provides no compensating maintenance signal.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap, not evidence of a specific defect.
The repository has no security policy, reducing guidance for reporting and handling vulnerabilities in a package intended for application integration.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 MohammadReza Honarkhah |
| sayad aazami |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ramsey/uuid Version ^3.0 | — | — |
doctrine/dbal Version ^2.5 | — | — |
jmikola/geojson Version ^1.0 | — | — |
geo-io/wkb-parser Version ^1.0 | — | — |
illuminate/database Version ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 11 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.