richard8768/encryption
A clear README, MIT licensing, repository tests, and release notes make the package understandable to adopt. Maintenance has been quiet recently, while one workflow uses an archived action and the repository has no security scanning.
68%
Total Score
50
83
50
Health Score Breakdown
Two releases in the last 12 months show ongoing publishing, but the median interval of about 403 days indicates a relatively slow release cadence.
The repository recorded zero commits and zero active maintainers in the last three months, weakening evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools are configured, leaving a meaningful repository hygiene gap for an encryption component.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a security-sensitive package.
Both workflows were analyzed completely with no untrusted checkout or script-injection findings, but all four action references are unpinned and one release workflow uses an archived action.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Eric Zhu |
| Taylor Otwell |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/di Version 3.2.* | — | — |
hyperf/helper Version ^3.2 | — | — |
hyperf/command Version 3.2.* | — | — |
hyperf/framework Version 3.2.* | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 3 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.