The repository is not archived and includes tests, a README, and a clear Apache-2.0 license. However, the release and commit history show prolonged inactivity, making abandonment and compatibility risk significant.
32%
Total Score
50
100
78
75
The latest release was published in June 2017, with no releases in the last 12 months despite 22 releases overall. This prolonged release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long period since its last release. This materially weakens confidence in ongoing maintenance.
There are no open issues or pull requests, and no recent issue or pull request activity. This is consistent with a dormant project, although the signal alone does not prove unresolved defects.
The repository has no stars or forks and only eight watchers. Popularity is supporting evidence rather than a verdict, but these low engagement levels provide no offset to the maintenance concerns.
Composer build tooling is present, but no security scanning tools were detected. This is a minor hygiene gap and does not outweigh the maintenance concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jbbcode/jbbcode Version ~1.3.0 | — | — |
open-orchestra/open-orchestra-base-bundle Version self.version | — | — |
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.