ncjoes/pdf-suite

Release historydanger

The latest release was about 9 years ago, with no releases in the last 12 months; this is strong evidence that the package is no longer maintained.

Repo commit activitydanger

There were no commits or active maintainers in the last 3 months, and the repository was last pushed about 9 years ago. This confirms a serious maintenance and abandonment risk.

Maintainerscaution

Only one registry account has publish access, which creates a thin publishing base. The linked repository is owned by the same individual, so there is no organizational backing shown to compensate for that concentration.

Repo issue activitycaution

There has been no issue or pull request activity recently, and there are no open issues or pull requests. With the equally inactive commit history, this reflects inactivity rather than a demonstrated resolution process.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. That leaves an assurance gap for a package handling external PDF-processing dependencies.