The repository has no commits in the past three months and no security scanning, which limits confidence in ongoing maintenance. Regular releases, a matching source repository, a license file, and no install scripts provide useful counterweight.
68%
Total Score
67
50
86
67
Six runtime dependencies create a moderate dependency surface for this configuration module, with no development dependencies declared. The surface is manageable but adds maintenance exposure.
Only one registry publishing account is listed. Because the project is backed by a user-owned repository rather than an organization, this indicates a thin publishing base, although release activity provides some compensation.
The repository recorded zero commits and zero active maintainers in the past three months. This weakens evidence of current maintenance, despite the recent release history.
Composer build tooling is present, but no security-scanning tools are reported. The missing scanning is a modest transparency and hygiene concern, not evidence that the package is unsafe.
The repository has no security policy. For a configuration library this is a transparency gap, though it is less serious than for a security-sensitive package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ra7/system_enums Version * | — | — |
ra7/system_exception Version * | — | — |
ra7/utils_filesystem Version * | — | — |
ra7/utils_normalizers Version * | — | — |
ra7/structure_singleton Version * | — | — |
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.