enterness/fbns-complement
The tiny project footprint and missing security process provide little evidence of resilience. MIT licensing, a clear README, and a stable 1.0 release make the package easier to inspect, but do not offset the lack of recent maintenance.
45%
Total Score
50
75
50
Health Score Breakdown
The package has only one release, published in September 2019, with no releases in the last 12 months. That long gap is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no updates since 2019.
The repository has 0 stars, 0 forks, and 1 watcher, so there is little visible community adoption or outside support to compensate for the inactive maintainer base.
Composer is used for builds, which is appropriate, but no security scanning tooling was detected. This reduces ongoing transparency for a package handling client connections and credentials.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is not evidence of a vulnerability itself.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Abyr Valg |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 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.