Documentation is still a template, and the project has no security policy or automated security scanning. Organization ownership and a matching repository provide provenance, but the package needs careful replacement planning.
45%
Total Score
50
67
75
The package has had only one release, published about 7 years ago, with no releases in the last 12 months. This strongly indicates the release line is abandoned, although it is not registry-deprecated.
The repository recorded no commits and no active maintainers in the last 3 months, with its last push about 4 years ago. This is strong evidence that maintenance has stopped.
The artifact includes a README and changelog, but the README contains placeholder text such as “This is where your description should go,” which weakens transparency for consumers.
Composer build tooling is present, but no security-scanning tools are configured. That reduces evidence of ongoing maintenance and security hygiene.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself show a vulnerability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phpoffice/phpword Version ^0.14.0 | — | — |
illuminate/support Version ~5 | — | — |
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.