jankx/post-layout
Documentation, licensing, and package structure give consumers a clear integration path. Maintenance evidence is thin, with only one release and no commits in the last three months; the repository also lacks a security policy and scanning.
61%
Total Score
75
100
88
83
Health Score Breakdown
The package has made only one release, about 14 months ago, with no releases in the last 12 months. This is meaningful abandonment risk for a new package, although the linked repository remains active enough to provide some backing.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single registry release, this lowers confidence in active maintenance.
Composer build tooling is present, but no security scanning tool is configured. That is a modest transparency and maintenance gap rather than a severe dependency risk.
The repository has no security policy. For a WordPress integration package, this leaves vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Puleeno Nguyen |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jankx/template Version * | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.