litzinger/basee
The project has a clear README, one runtime dependency, and a recent stable release. A single maintainer, no commits in three months, no security policy, and conflicting license evidence leave meaningful maintenance and transparency concerns.
62%
Total Score
67
100
89
75
Health Score Breakdown
The manifest declares MIT, but the artifact's detected license is Apache-2.0; although license files exist in both the package and repository, the mismatch creates legal uncertainty.
Only one registry publishing account is listed. Because the project is user-owned rather than organization-owned, this indicates a thin publishing and continuity base.
The repository recorded no commits and no active maintainers in the last three months. The recent release partly offsets this, but the current development pause raises maintenance risk.
Composer is used as the build tool, but no security scanning tools are configured. The build setup is clear, while the missing automated security checks are a modest hygiene gap.
The repository has no security policy, leaving no documented channel or process for reporting and handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Brian Litzinger |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 10 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.