christophwurst/kitinerary
The clear README, license, and minimal dependency profile make adoption straightforward. The missing security policy and absent security tooling reduce maintenance visibility for a package that has not changed recently.
58%
Total Score
50
100
79
83
Health Score Breakdown
The package has had 6 releases since November 2019, but none in the last 12 months; its latest release was in October 2023, nearly 3 years ago. This is a meaningful maintenance concern, though the package is small and not marked deprecated.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Combined with the old latest release, this indicates little current maintenance capacity.
Composer is used as the build tool, but no security scanning tools are configured. The build setup is appropriate, while the lack of scanning is a modest transparency gap.
The linked repository is not archived, although its last push was in December 2023. The active status is reassuring, while the old push date aligns with the maintenance concern.
The repository has no security policy. For a package that may process itinerary data, this reduces clarity about vulnerability reporting and response.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Christoph Wurst |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 6 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.