A toolkit with lots of helpers for users and accounts
82%
Total Score
70
100
94
80
Only one registry publishing maintainer, ByMayo, is listed. This is a continuity concern for a user-owned project because publishing capability is concentrated, with no organization backing shown by the project_backing signal.
The repository owner is the user account bymayo rather than an organization, so the single-maintainer and bus-factor concerns are not mitigated by organizational backing.
All 10 commits in the last three months came from one contributor, giving a 100% top-contributor share. Without organization backing or a second active contributor, this creates a genuine continuity risk.
Composer is used as a build tool, but no security scanning tools are detected. The build tooling is appropriate, while the missing scanning reduces supply-chain transparency.
No repository security policy is present. This is a transparency gap for a plugin handling authentication, passwords, magic links, and account operations, although its absence alone does not demonstrate unsafe maintenance.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-10320 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. bymayo/porter is vulnerable to Cross-Site Request Forgery (CSRF) in versions 1.0.0 - 5.0.4. | 1.0.0 - 5.0.4 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.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.