The dependency set is broad, and the repository has neither a security policy nor automated security scanning, increasing maintenance overhead. The package is licensed and documented, with regular releases, but recent repository activity is absent.
65%
Total Score
50
50
94
50
Twenty-five runtime dependencies, including WordPress plugins and build-related components, create a broad maintenance and transitive-update surface for a starter package.
Three install and update lifecycle scripts run during project creation or dependency operations, adding execution complexity and requiring trust in the package's setup behavior.
The repository is owned by an individual rather than an organization, so there is no indicated organizational capacity to offset the thin visible maintenance activity.
There were no commits and no active maintainers in the last three months, a meaningful sign of slowing maintenance despite the package's release history.
Composer is used for builds, but no security scanning tool is configured, leaving a repository-level maintenance and transparency gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
timber/timber Version ^2.3.3 | — | — |
oscarotero/env Version ^2.1.1 | — | — |
roots/wordpress Version ^6.8.3 | — | — |
roots/wp-config Version 1.0.0 | — | — |
vlucas/phpdotenv Version ^5.6.2 | — | — |
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.