yzyblog/coffice_service

Release historydanger

The latest release was in September 2017, with no releases in the last 12 months despite the package being over nine years old. This is strong evidence of abandonment risk.

Dependency profilecaution

The package declares only two runtime dependencies and no development dependencies, which is a small dependency surface. The lack of development dependencies also provides little evidence of maintained testing or development practice.

Licensecaution

The manifest declares “1.0.0,” which is not a recognised license, and no license file was found in either the package or repository. Consumers therefore lack clear reuse terms.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to offset the package’s single-maintainer and inactivity concerns.

Repo popularitycaution

The repository has one star and no forks, providing little community evidence or external review. Popularity is supporting evidence rather than decisive on its own, but it does not compensate for the inactivity.