blomstra/search
The MIT license, clear README, and organization ownership support adoption. Pinning the workflow action and adding security scanning would improve release hygiene.
62%
Total Score
75
100
81
67
Health Score Breakdown
The package has existed for about 4 years and has 42 releases, but only one release appeared in the last 12 months, indicating a slow recent cadence.
The repository recorded no commits and no active maintainers in the last 3 months, which is a concrete sign of currently limited maintenance activity.
There were no new or closed issues or pull requests in the last month, alongside six open issues and one open pull request; this suggests limited recent project interaction.
Composer build tooling is present, but no security scanning tools are configured, leaving a modest repository hygiene gap.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Team Blomstra |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 flarum/core Version ^1.2.0 | — | — |
elasticsearch/elasticsearch Version 7.* | — | — |
spatie/elasticsearch-query-builder Version ^1.3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 months ago
- Created
- 4 years 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.