Log browser errors to the server using W3C Reporting API
72%
Total Score
67
100
94
80
Only one registry account has publishing access. The repository is owned by the same individual rather than an organization, so the narrow maintainer base leaves limited visible redundancy.
The project has existed for about 8 years and has 12 releases, but only one release appeared in the last 12 months, indicating a slow maintenance cadence.
There were no commits and no active maintainers in the last three months. Although the repository was pushed about 2 months ago, the absence of recent commit activity is a meaningful maintenance concern.
No repository security policy was found. This is a transparency gap for a package that processes browser error reports, though the repository does use Dependabot and security scanning.
The workflow lacks top-level token permissions and relies on job-level permissions only, so its least-privilege configuration is less explicit than ideal.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^9.0|^10.0|^11.0|^12.0|^13.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.