Usable with caveats: the package is actively released, backed by an organization, and not deprecated or archived. However, no commits were recorded in the last three months, and the release workflow lacks top-level token permissions and a repository security policy.
68%
Total Score
88
100
89
80
The artifact lacks a README, tests, and changelog, which reduces release transparency. The repository file tree nevertheless includes a test file and GitHub Releases are used, partly compensating for the artifact gaps.
No commits and no active maintainers were recorded in the last three months, which is a meaningful maintenance concern. The recent release and repository push show current publishing activity but do not fully offset the absence of recent commits.
The repository has no stars or forks and only 9 watchers, showing limited external adoption. Popularity is supporting evidence, so this lowers confidence in broad community resilience but does not make the package unsafe by itself.
No repository security policy was found, leaving vulnerability-reporting guidance undocumented. This is a transparency gap, but it is not evidence that the package is unmaintained or unsafe on its own.
The release workflow has no top-level token permissions and relies on job-level permissions, with no read-only top-level declaration. This weakens workflow permission clarity and increases configuration risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
helsingborg-stad/wpservice Version ^2.0 | — | — |
helsingborg-stad/wputilservice Version ^0.3 | — | — |
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.