frizinak/zip-streamer

Release historydanger

The latest release was published in April 2017, with no releases in the last 12 months. This is strong evidence of an unmaintained dependency, although the package has five releases overall.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, with its last push in April 2017. This indicates prolonged inactivity and raises abandonment risk.

Repo package mentioncaution

The repository name does not match the package name, and its README does not mention the package. That makes the package-to-source relationship harder to verify, even though the repository URL uses the same publisher account.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. That is a maintenance and transparency gap for an old dependency, though it is not evidence of malicious behavior.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a modest transparency gap, especially for a package that streams files and network content.