The package is small and easy to inspect, with a short README and three runtime dependencies. Its organization-backed repository remains unarchived, but long release gaps and no recent commits make ongoing support uncertain.
58%
Total Score
75
100
75
75
Only two releases have appeared across 882 days, with a median interval of about 871 days and one release in the last 12 months. The recent 1.0.1 release helps, but the overall cadence is sparse.
The repository recorded zero commits and zero active maintainers in the last three months. The recent push associated with the release is not enough to demonstrate continuing development.
The repository name does not match the package name and its README does not mention the package. Although this could reflect a packaging or monorepo arrangement, the collected evidence leaves package ownership less transparent.
Composer build tooling is present, but no security scanning tools were detected. This modestly reduces evidence of automated security hygiene without indicating that the release is unsafe.
The repository has no security policy. This is a modest transparency gap for a package that can be used in application infrastructure, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phore/system Version * | — | — |
phore/filesystem Version * | — | — |
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.