raxos/container
The project has a very small source tree and limited security safeguards. MIT licensing, frequent releases, and a non-archived repository provide useful support, but no commits in the last three months limits confidence in ongoing maintenance.
61%
Total Score
50
88
75
Health Score Breakdown
One registry maintainer is a thin publishing base, and the repository is owned by an individual rather than an organization. Frequent releases partly compensate, but do not remove the continuity risk.
The package includes a README, but it is only 248 characters and provides little integration guidance for a container library. Missing tests and changelog files are normal for a published artifact and are not concerns here.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release cadence is a compensating signal, but this still weakens evidence of ongoing development.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful repository hygiene gap for a package intended to be consumed as a dependency.
The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Bas Milius |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 raxos/error Version * | — | — |
raxos/contract Version * | — | — |
raxos/foundation Version * | — | — |
jetbrains/phpstorm-attributes Version ^1.2 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 12 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.