Avro for JavaScript
65%
Total Score
50
100
90
83
50
No build attestation, trusted publisher, or staged publishing is recorded, leaving the origin of this release less verifiable than it could be.
Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although registry access is not evidence of actual development activity.
The repository is owned by an individual account rather than an organization, so the single registry maintainer provides no visible organizational continuity.
The package is mature, with 165 releases over roughly 11 years, but it had no releases in the last 12 months after its latest release on July 13, 2025. That is a meaningful maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months. This is the strongest abandonment concern, even though the repository was pushed more recently than that window.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.