annotation/larscan
A single maintainer, no tests, and no security policy limit confidence in ongoing care. MIT licensing, a usable README, and organization-backed ownership provide useful transparency.
55%
Total Score
67
100
81
75
Health Score Breakdown
Only one registry account has publish access, which increases publishing bus-factor risk, although the organization-backed repository provides some compensating project context.
The package has three releases, but none in the last 12 months and the latest release was roughly 16 months ago, indicating stalled maintenance for a young package.
The repository recorded no commits and no active maintainers in the last three months, leaving no evidence of current development activity.
Composer build tooling is present, but no security-scanning tooling was detected; this is a modest transparency and maintenance weakness rather than a severe risk.
The linked repository is not archived, but its last push was roughly 20 months ago, which is consistent with the broader maintenance slowdown.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 jundayw |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 rfc/scannable Version ^1.0 | — | — |
illuminate/support Version >=8.0.0 | — | — |
reflective/reflection Version ^2.0 | — | — |
illuminate/collections Version >=8.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.