There is no security policy or observed security scanning, and the repository has minimal community activity. The BSD-3-Clause license and organization-owned repository provide useful transparency, but do not offset the maintenance concern.
42%
Total Score
100
64
75
The latest release was about seven years ago, with no releases in the last 12 months. That prolonged inactivity is strong evidence of abandonment risk, despite the package having 15 releases and a stable final version.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of an active user or contributor community.
Composer is used for the build, but no security-scanning tooling is present. The missing scanning is a hygiene concern, while the standard build tool is a small compensating signal.
The repository is not archived, which preserves a path for future maintenance, but its last push was also about seven years ago and therefore does not offset the inactivity shown by release_history.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a modest transparency gap for a library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gobline/auth Version ^2.0 | — | — |
gobline/form Version ^1.0 | — | — |
gobline/flash Version ^2.0 | — | — |
gobline/router Version ^3.0 | — | — |
gobline/mediator Version ^3.0 | — | — |
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.