It has clear ownership, a matching repository, tests, a changelog, and consistent MIT licensing. Its long inactivity and unpinned workflow actions increase maintenance and build-integrity risk.
58%
Total Score
50
100
81
75
The registry namespace and repository are owned by the same individual, so the ownership context is consistent. A single-user project can still have limited maintenance capacity.
The package has six releases since March 2016, but none in the last 12 months and the latest release was in September 2021. This indicates a long period without published maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest push, this materially raises abandonment risk.
There are no open issues or pull requests, and no issue or pull-request activity in the last month. This is consistent with a quiet project but provides no evidence of active maintenance.
The repository uses Make and Composer, showing basic build structure, but it has no security-scanning tools. That is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/stopwatch Version ^3.0|^4.0|^5.0 | — | — |
influxdb/influxdb-php Version ^1.2 | — | — |
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.