There is no security policy or security-scanning tooling, and the repository name does not match the package name. Tests, licensing, recent releases, and recent repository activity provide useful support, but all recent commits come from one contributor.
68%
Total Score
67
100
79
75
The repository is owned by an individual user rather than an organization, so the single-contributor concentration is not offset by visible organizational backing.
All 18 recent commits came from one contributor, leaving maintenance highly concentrated and creating meaningful continuity risk if that contributor stops.
The repository name does not match the package name and the package name was not found in the README. That mismatch raises uncertainty about repository ownership or package provenance, though the matching source tree and tests provide some compensation.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a transparency and maintenance caution, not a severe risk on its own.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
alcamo/markdown Version ^0.1 | — | — |
alcamo/rdf-literal-workbench Version ^0.2 | — | — |
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.