ksfraser/ksf-project-management
Tests, documentation, a declared MIT license, and no install-time scripts provide useful baseline transparency. However, this young pre-1.0 project shows no commits in three months, ten open issues, and a repository/package-name mismatch.
55%
Total Score
25
100
71
75
Health Score Breakdown
The repository recorded zero commits and zero active maintainers in the last three months, a meaningful maintenance warning for a package released only four times.
The package is only 146 days old and has four releases, with a median interval of about 6 hours, indicating active initial publishing but limited history for judging long-term maintenance.
Ten issues remain open, while no issues or pull requests were opened or closed in the last month, suggesting unresolved work and limited recent project interaction.
The repository name does not match the package name and its README does not mention the package, so the source-to-package relationship is not clearly established.
Composer build tooling is present, but no security-scanning tool was detected, leaving repository security hygiene less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ksfraser/ksf-common-db Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 5 months 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.