Package Health

headoo/annotations

There is no security policy or automated security scanning, which weakens transparency for long-term maintenance. MIT licensing, a README, and repository tests make the code easier to evaluate, but do not offset the maintenance concern.

Latest v2.0PackagistPackagist

38%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

50

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

67

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

75

Health Score Breakdown

Release historydanger

The package has had no release in more than 11 years; all nine releases occurred on the same day in 2015, indicating severe abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no work since 2015.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a maintenance and transparency gap.

Repository archivedcaution

The repository is not archived, which preserves a path for future maintenance, but its last push was in 2015 and does not offset the inactivity evidence.

Security policycaution

The repository has no security policy, leaving no documented process for receiving or disclosing vulnerabilities.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Roman Borschel
Benjamin Eberlei
Guilherme Blanco
Jonathan Wage
Johannes Schmitt

Direct Dependencies

DependencyLast ReleaseScore
doctrine/lexer
Version 1.*

Weekly Downloads

Info

Last Published
11 years ago
Created
13 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.

Aikido Platform