The package includes tests in its repository, a release note, and a clear MIT license, but it lacks a security policy and shows little community traction. Treat this as a legacy dependency and pin the exact version if adoption is unavoidable.
42%
Total Score
0
67
83
Only one release exists, published about 6 years and 7 months ago, with none in the last 12 months. This is strong evidence of an unmaintained package despite the repository not being archived.
The repository had zero commits and zero active maintainers in the last 3 months, consistent with the package's long release silence and increasing abandonment risk.
The repository name does not match the package name and its README does not mention the package, so the linkage is less transparent even though the repository file tree contains the package sources.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is not required for a healthy small package, but these counters provide no supporting evidence of active community oversight.
The repository has no security policy. This is a transparency and response-process gap, especially for a dependency that has not received maintenance activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
fize/net Version ~4.0 | — | — |
fize/misc Version ~0.1 | — | — |
fize/crypt Version ~3.2 | — | — |
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.