Milpa Framework — core contracts and primitives. Framework-agnostic: no ORM, no HTTP client, no host-application coupling (ADR-001).
78%
Total Score
80
100
83
90
Only one account has registry publish access. This is a modest publishing bus-factor concern, though the repository is organization-owned and the active source history provides some compensation.
One contributor authored all 32 commits in the last three months, creating a genuine continuity risk. Organization ownership partly mitigates handoff concerns, but no second active contributor is shown by this signal.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers external validation but is not independently a serious health defect for a young package.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanner is a security-process gap rather than evidence of poor maintenance, and other repository hygiene signals are positive.
All analyzed workflows declare top-level permissions; one is read-only and three request write permissions. Explicit permissions are better than implicit defaults, though write access increases the impact of a workflow compromise.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2.0 | — | — |
symfony/event-dispatcher-contracts Version ^3.0 | — | — |
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.