Clear licensing, documentation, release notes, tests in the source tree, and security scanning improve transparency. The project is only three days old, with rapid releases and no recorded three-month commit activity, so longer-term stability remains unproven.
72%
Total Score
75
100
94
67
Twenty releases in three days, with a median interval of about 20 minutes, show active publishing but also reflect a very new project whose release process has not matured.
No commits are recorded in the prior three months and no active maintainers are reported for that period. Because the project is only three days old, this mainly means there is not yet a meaningful maintenance history rather than proven abandonment.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear for a plugin that handles database exports and credentials.
Both workflows were fully analyzed with no untrusted checkouts, script injection, or audit findings. However, all 3 action references are unpinned and one workflow grants top-level write access, creating moderate workflow hygiene concerns.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
helsingborg-stad/wpservice Version 2.0.9 | — | — |
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.