dbeurive/lexer

Release historydanger

The package has had no release in nearly 10 years; all five releases arrived within about four days in November 2016, showing a completed but abandoned release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, with its last push in November 2016. This is strong evidence that maintenance has stopped.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad support community.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning reduces oversight of future changes, while the package's zero runtime dependencies limit exposure.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious for a small dependency-free package.