staffkojinpro/microsoft-teams

Release historydanger

The package has had no release in over four years, with zero releases in the last 12 months. This is a substantial maintenance concern despite its eight total releases.

Repo commit activitydanger

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

Project backingcaution

The package and repository are owned by the same individual account, so there is no organizational backing to offset the thin maintenance history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Repository archivedcaution

The repository is not archived, although its last push was over three years ago. Continued availability compensates for some abandonment concern but not the lack of recent activity.