sbuerk/typo3-cmscomposerinstallers-testingframework-bridge
The small scope, clear README, and release notes make its purpose easy to verify. The license is clear, but workflow dependencies are unpinned and repository security documentation is absent.
56%
Total Score
0
75
67
Health Score Breakdown
The repository had zero commits and zero active maintainers in the last three months, consistent with the last push being about three years ago. This materially raises abandonment risk.
The latest release was about three years ago, with no releases in the last 12 months. Earlier releases were regular enough to show a real project, but current maintenance appears stalled.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Version 0.1.3 is a non-stable-major release, which signals a compatibility-oriented project with a greater risk of breaking changes than a mature 1.x package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Stefan Bürk |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years 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.