The project has tests, a clear README, licensing, and recent repository activity. Its release history is sparse, commits stopped for three months, and all three workflow actions are unpinned; no security policy is also documented.
62%
Total Score
50
100
94
75
One registry publishing account is consistent with this user-owned project, but it provides limited publishing redundancy.
The registry namespace and repository are owned by the same individual account, so ownership is consistent, though there is no organizational backing to broaden maintainer capacity.
Only two releases exist over roughly three years, with one release in the last 12 months and a median interval of about 933 days. This sparse cadence limits evidence of mature maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. That recent inactivity raises maintenance and abandonment concerns, although the repository was pushed more recently overall.
There are no open issues and two open pull requests, but no issues or pull requests were opened or merged in the last month. This gives little evidence of active project interaction.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
itinerisltd/itineris-wp-coding-standards Version ^1.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.