bdk/errorhandler
Tests, a README, and release notes support practical use, but recent commit activity is absent and the project has only one registry maintainer. The workflow uses four unpinned actions, including one from an archived repository, and has no security policy.
68%
Total Score
50
100
100
67
Health Score Breakdown
Only one account has registry publish access, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided organizational backing to offset that concentration.
No commits and no active maintainers were recorded in the last 3 months. The recent release and repository push provide some counterweight, but this still weakens evidence of ongoing development.
The repository has no security policy, leaving vulnerability-reporting and response expectations unclear for a package handling errors.
The sole workflow was fully analyzed and has no untrusted checkout or script-injection findings, but all 4 action references are unpinned and one high-confidence medium-severity finding uses an archived action. No top-level permissions block is not a concern on its own here.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Brad Kent |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 bdk/pubsub Version ^3.2.2 | — | — |
bdk/backtrace Version ^2.2.4 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 6 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.