Package Health/coraxster/flysystem-owncloud

coraxster/flysystem-owncloud

The MIT license and matching repository make the package transparent, but its minimal four-file project offers little evidence of testing or security practice. Pinning this sole release leaves you dependent on a project with no activity since September 2017.

Latest 1.0.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over nine years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a dependency that may need compatibility or security fixes.

Repo commit activity

There were zero commits and zero active maintainers during the last three months, matching the repository’s last push in 2017. This is the clearest maintenance and abandonment concern.

Package file tree

The artifact and repository each contain only four files, including one source file and no test suite. This very small surface may be appropriate for an adapter, but it provides limited evidence of maturity and maintenance discipline.

Project backing

The package and repository are owned by the same individual account rather than an organization. Combined with one registry maintainer and no recent activity, this indicates limited visible backing for recovery or continued maintenance.

Repo issue activity

One issue remains open, while there has been no issue or pull-request activity in the last month. This is consistent with a project receiving no recent maintenance attention.