teamones/log

Release historydanger

Only two releases were published, both in February 2021, and there have been no releases in over five years. This is strong evidence of abandonment risk for a package intended as a runtime dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long gap since the last release. This materially increases abandonment risk.

Maintainerscaution

Only one account has registry publishing access. The organization-backed repository partly compensates, but a single publisher remains a resilience concern.

Package file treecaution

The package contains only four files, including one source file and its manifest. This is transparent and easy to inspect, but the very small project footprint offers limited evidence of maturity.

Repo issue activitycaution

There were no recent issues or pull requests. With no open work this is not inherently negative, but it also shows no recent community activity to offset the lack of commits.