tomato-technologies/tomato-pdfmerger

Release historydanger

This is the only release, published in January 2019, with no releases in the last 12 months. That long period without a new version is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release inactivity.

Lifecycle scriptscaution

A post-install command runs during installation, adding execution behavior beyond dependency resolution. No provided signal shows that this script is necessary or independently documented.

Repo toolingcaution

Composer is used for the build, but the repository has no security scanning tools. For a small wrapper this is a modest transparency and maintenance gap, not evidence of unsafe code.

Security policycaution

The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This weakens maintenance transparency, especially for a package that has seen no recent development.