The package has a clear README, tests, a matching repository, and a small runtime dependency footprint. Organization backing and no install scripts reduce adoption friction.
58%
Total Score
75
100
71
83
The package has 31 releases, but they were concentrated between April 10 and April 12, with a median interval of about 9 hours and only 4 releases in the last 12 months. This shows an initially active burst without sustained release evidence.
The repository recorded zero commits and zero active maintainers in the last three months, with the last push about five months earlier. For a package only about five months old, this is a meaningful maintenance and abandonment concern.
The repository has zero stars, forks, and watchers, so there is no community adoption evidence to support maturity. Popularity is supporting evidence only, and the package's young age limits how strongly this should count.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are reported. The missing scanning is a hygiene gap rather than evidence of unsafe code.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a process gap rather than a direct indication that the release is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
preflow/core Version ^0.1 || @dev | — | — |
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.