jacekbarecki/flysystem-onedrive

Release historydanger

The package has only two releases, both in February 2016, with no release in about 10 years. This strongly indicates abandonment, although the short initial release interval shows it was once published deliberately.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, and its last push was about 8 years ago. This is strong evidence that maintenance has stopped.

Maintainerscaution

A single registry maintainer creates a thin publishing base and increases continuity risk. The matching source repository and clear project ownership provide some traceability but do not offset the lack of recent activity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest supply-chain hygiene gap rather than evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy. For an old filesystem adapter this is a transparency and vulnerability-reporting gap, though it is less significant than the stopped development activity.