Exception components for the byteShard framework
62%
Total Score
75
100
88
75
The package has had four releases since May 2023, but none in the 12 months before the September 2026 assessment; the latest release was about 16 months ago. This indicates materially reduced maintenance activity for a dependency.
The repository had zero commits and zero active maintainers in the three months before collection. This corroborates the long release gap and raises abandonment concern.
Composer build tooling is present, but no security-scanning tool was detected. This is a minor transparency and hygiene gap rather than evidence of unsafe behavior.
The repository has no security policy. For a small exception library this is a limited concern, but it leaves vulnerability-reporting expectations undocumented.
The single workflow was fully analyzed with no injection or high-confidence audit findings, but all four action references are unpinned. That leaves the build exposed to unexpected action changes and is a workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
byteshard/enum Version ^1.0 | — | — |
byteshard/locale Version ^1.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.