sly/parsecom-manager

Licensedanger

No license is declared and no license file was detected in either the package or repository. Without licensing terms, adoption creates a material legal and transparency concern.

Release historydanger

There has been only one release, published in December 2014, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo issue activitycaution

There is one open issue and no issues or pull requests were created, closed, or merged in the last month. This supports the conclusion that the project is inactive, though the small project size limits how much activity would be expected.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. The tooling is appropriate for the package, while the missing scanning is a modest transparency gap rather than a decisive risk.

Repository archivedcaution

The linked repository is not marked archived, which avoids an explicit abandonment signal. However, its last push was in December 2014, so this does not offset the stale release history.