tnhnclskn/yify-api

Release historydanger

This is the package's only release, published about 2 years and 6 months ago, with no releases in the last 12 months. That materially weakens evidence of ongoing maintenance.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, consistent with the long release gap and increasing abandonment risk.

Maintainerscaution

The registry lists one maintainer. That is workable for a small user-owned project, but it provides little redundancy if that person stops maintaining it.

Package file treecaution

The package and repository contain a small, matching five-file tree, making the published contents transparent, though it also shows a very limited project footprint.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a release-blocking problem.