uic-dev/picofeed

The repository has no security policy or automated security scanning, increasing uncertainty for a library that processes feed content. MIT licensing, a clear package tree, and release notes provide useful transparency, but not enough to offset the weak maintenance evidence.

Latest v1.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made only one release, on October 16, 2018, with no releases in the last 12 months. This is strong evidence of abandonment for a maintained dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for years. This materially increases abandonment risk.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a feed-processing library, the missing automated security checks reduce maintenance transparency.

Repository archived

The repository is not marked archived, but it was last pushed on October 16, 2018. The lack of archival status is mildly reassuring but does not show active maintenance.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency gap for a library that consumes remote feed data.