Healthy and suitable to use, with a small maintenance team as the main caveat. It has a long release history, recent releases, matching source code, repository tests, and no deprecation or install-time scripts; all recent commits come from one contributor.
78%
Total Score
83
89
88
All 3 recent commits came from one contributor, creating a genuine continuity risk. The organization-owned repository provides some ability to hand maintenance off, but no second active contributor is shown.
The repository has only 1 star and no forks, indicating a small user and contributor footprint. Popularity is supporting evidence rather than a decisive health judgment, and the active release history offsets much of this concern.
Composer build tooling is present, but no security scanning tools are reported. This is a modest transparency and assurance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. The gap lowers transparency but is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wedeto/io Version ^1.1.0 | — | — |
wedeto/util Version ^1.1.7 | — | — |
wedeto/fileformats Version ^1.1.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.