sandstorm/kissearch
Healthy and reasonable to adopt. It has frequent stable releases, current repository activity, tests, clear documentation, and organization backing; the main caveat is that all recent commits come from one maintainer and no security policy is present.
82%
Total Score
83
100
94
83
Health Score Breakdown
All four recent commits came from one contributor, creating a real continuity risk. Organization backing partly compensates because maintenance can potentially be handed off within the organization.
Composer is used as the build tool, but no security scanning tools are configured; the missing scanning is a transparency gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/flow Version >=9.2 <10.0.0 | — | — |
neos/neos Version >=9.2 <10.0.0 | — | — |
neos/neos-ui Version >=9.2 <10.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 days ago
- Created
- 1 year 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.