A README, tests, and a small dependency set help integration, but the project has no security policy and no adoption signals. The repository/package naming mismatch also makes ownership less transparent.
34%
Total Score
33
100
61
75
The package has only two releases, with the latest about 12 years ago and none in the last 12 months. This is strong evidence of abandonment for a library dependency.
The repository had zero commits and zero active maintainers in the last three months, after its last push about 12 years ago. This materially raises abandonment risk.
The package and repository are owned by the same individual account, so the source ownership is at least aligned. This provides limited backing because no organization support is shown.
There are no open issues or pull requests and no recent issue or pull request activity. This does not prove abandonment alone, but it offers no evidence of active maintenance.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository directly corresponds to this package rather than a similarly named project.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzle/guzzle Version 3.* | — | — |
jongotlin/affiliate-interfaces Version 0.1.1 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.