Revolt event loop lifecycle and config integration for Marko Framework
72%
Total Score
caution
Twenty-five releases in 194 days show momentum, but zero commits or active maintainers in the last three months limit confidence.
The repository records zero commits and zero active maintainers in the last three months, despite frequent registry releases; this weakens confidence in ongoing source maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, which reduces the available guidance for reporting and handling vulnerabilities.
Version 0.11.0 is not a prerelease, but it remains on a 0.x major version, so compatibility expectations are somewhat less mature than for a stable major release.
No GitHub Actions workflows were found, so this audit found no workflow-specific dangerous triggers, permissions, or unpinned actions. It also provides no evidence of automated CI or release checks.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
amphp/amp Version ^3 | — | — |
marko/core Version self.version | — | — |
marko/config Version self.version | — | — |
marko/pubsub Version self.version | — | — |
revolt/event-loop Version ^1 | — | — |
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.