liagkos/vatidinfo

Release historydanger

The latest release was published over six years ago, with no releases in the past 12 months. The seven-release history shows the package was once active but does not offset the prolonged release gap.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push, this is strong evidence that maintenance has stopped.

Maintainerscaution

One registry publisher is a thin publishing base for a user-owned project. This is not proof of abandonment, but it provides limited visible maintenance capacity alongside the inactive repository.

Project backingcaution

The package and repository are owned by the same individual account, so the source identity is clear, but there is no organizational backing shown to compensate for the thin maintainer base.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a release-blocking issue.