Documentation and tests are present, and the repository is licensed and not archived. The single-maintainer project lacks a security policy and automated security scanning, limiting ongoing assurance.
54%
Total Score
25
75
75
The package has only two releases, with no release in roughly 10 years. That strongly raises abandonment risk for a dependency, though the package remains available and is not marked deprecated.
The repository recorded no commits or active maintainers in the last three months, and its last push was in 2016. This indicates the project is effectively inactive, despite not being archived.
Only one registry maintainer is listed, which leaves publishing continuity dependent on a single person. The linked repository is also user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
Composer build tooling is present, but no security-scanning tool was detected. That weakens evidence of continuing supply-chain and dependency oversight.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This is a transparency and ongoing-assurance gap for a package intended to process files.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jstewmc/read-file Version ^0.1 | — | — |
jstewmc/write-file Version ^0.1 | — | — |
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.