WordPress Composer Starter Repo
34%
Total Score
unhealthy
Risky: no releases or commits since April 2018, with 12 open issues and no security policy.
The package has had no release in more than 8 years: its latest release was April 10, 2018, with zero releases in the last 12 months. This is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last 3 months, consistent with the repository's last push in April 2018. This materially increases the risk that defects and dependency changes will go unattended.
The repository has 12 open issues but no new or closed issues and no pull-request activity in the last month. Combined with the old release history, this suggests unresolved maintenance demand.
Composer build tooling is present, but no security-scanning tooling is configured. This is a modest transparency and maintenance gap, though it does not outweigh the direct inactivity evidence.
The linked repository has no security policy. That leaves vulnerability reporting and response expectations unclear, adding a transparency concern for a package that installs WordPress and multiple runtime dependencies.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
vlucas/phpdotenv Version 2.4.* | — | — |
illuminate/config Version 5.5.* | — | — |
johnpbloch/wordpress Version 4.9.4 | — | — |
illuminate/filesystem Version 5.5.* | — | — |
wpackagist-plugin/wordpress-seo Version 7.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.