Tests are present, the package declares MIT licensing, and it has no install-time scripts. Its only release was about 10 years ago, while the repository has had no push since then; the repository/package name mismatch also weakens provenance.
38%
Total Score
50
60
75
The package has only one release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The package declares four runtime dependencies, including three project-specific packages. This is not excessive, but the dependency chain adds maintenance surface to an already stale release.
The repository name does not match the package name, and no README mention was available. That weakens confidence that the linked repository clearly represents this package.
The linked repository is not archived, which is a compensating sign, but its last push was about 10 years ago and does not offset the lack of recent release activity.
The repository has no security policy. For a small, inactive package this reduces transparency and reporting clarity, though it is less important than the demonstrated lack of maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hindy/helper Version 0.* | — | — |
hindy/template Version >=1.0.3 | — | — |
hindy/exception Version 0.* | — | — |
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.