It has a clear README, tests, MIT licensing, and no install-time scripts. The package is small and directly matches its repository, but offers no security scanning or policy.
58%
Total Score
50
79
50
The package has had no release in over three years, with only four releases overall and none in the last 12 months. This is a substantial maintenance concern, though the repository is not archived.
There were no commits and no active maintainers in the last three months, consistent with the long release gap. This raises abandonment risk, but the repository is intact and the package remains narrowly scoped.
Composer build tooling is present, but no security-scanning tool was detected. That reduces assurance for dependency maintenance without making the release unfit on its own.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package intended to be reused as a dependency.
The assessed release is v0.1.0, so the public API may still change and the project has limited maturity evidence. It is not marked as a prerelease, which partly offsets the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
danidoble/translation Version * | — | — |
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.