The small dependency footprint, MIT license, and repository tooling reduce adoption friction. Maintenance evidence is mixed: the registry shows no release in over four years, while the repository is not archived but recorded no commits in the last three months. The repository does not clearly identify the package, adding uncertainty.
58%
Total Score
50
100
80
50
The latest release was over four years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the seven-release history shows the package was previously developed.
The repository recorded zero commits and zero active maintainers in the last three months. The repository's later push timestamp provides some compensating evidence, but current development activity remains unclear.
The linked repository name does not match the package name, and no README mention was available. This creates uncertainty about whether the repository is the package's primary source, though a sub-package repository can legitimately use a different name.
The repository has no published security policy. This is a transparency gap for reporting and handling vulnerabilities, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
dot/platform Version 0.5.* | — | — |
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.