apishka/transformer
The stable release includes broad tests and no install-time scripts, which supports predictable use. Its single maintainer and absent security policy add uncertainty around future upkeep.
44%
Total Score
50
100
81
83
Health Score Breakdown
The package has had no release in more than seven years, despite 44 releases overall. Its earlier cadence shows past activity but does not offset the prolonged release gap.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push in 2019. This is strong evidence of abandonment risk.
Only one registry maintainer is listed, which creates a thin publishing base. Organization backing partly compensates because the repository is owned by an organization.
Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This matters more because the project also shows no recent maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Evgeny Reykh |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nesbot/carbon Version ^2.0.0 | — | — |
apishka/singleton Version ^1.0.1 | — | — |
apishka/easy-extend Version * | — | — |
egulias/email-validator Version ^2.1.3 | — | — |
Weekly Downloads
Info
- Last Published
- 7 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.