The README, changelog, repository tests, and MIT licensing provide useful documentation and transparency. Its single release and absent recent repository activity leave maintenance and compatibility uncertain for a new dependency.
38%
Total Score
33
69
75
This package has only one release, 0.0.1, published more than eight years ago, with no releases in the last twelve months. That strongly raises abandonment and compatibility risk.
There were no commits or active maintainers in the last three months, consistent with the repository's last push being in December 2017. This is substantial evidence of inactivity.
Only one registry account has publishing access. That can be normal for a small user-owned project, but it leaves limited visible publishing redundancy when there is no recent activity.
The repository is owned by an individual rather than an organization, and no broader organizational backing is shown. Combined with the lack of recent activity, this provides limited maintenance assurance.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counters provide little supporting evidence of community adoption.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jdr/event-recorder Version ^0.0.2 | — | — |
jdr/event-recorder-doctrine-bridge Version ^0.0.1 | — | — |
jdr/event-recorder-tactician-bridge Version ^0.0.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.