maslosoft/binder
The mixed AGPL/proprietary licensing needs a deliberate fit for your project. Tests, a changelog, no runtime dependencies, and an unarchived organization-backed repository provide useful support.
58%
Total Score
75
100
70
50
Health checks
The manifest declares both AGPL-3.0-only and proprietary licensing, with no license file detected in the package or repository. This creates meaningful uncertainty about which usage rights apply.
The package has 74 releases since May 2015, but none in the last 12 months and its latest release was on June 30, 2023. This long gap materially raises abandonment risk despite the historically regular release cadence.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release gap. The repository is not archived, but there is no recent development activity to offset the concern.
Composer is used as a build tool, but no security scanning tools are configured. This is a modest transparency and hygiene gap rather than evidence of abandonment.
The repository has no security policy. That limits the project's documented process for receiving and coordinating vulnerability reports, though it is not independently evidence of an unsafe release.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Peter Maselkowski |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 11 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.