clockster/sdk

Release historycaution

The package is only 40 days old with four releases and a median interval of about 8 days. The regular cadence is positive, but the short history provides little evidence of durable maintenance.

Repo bus factorcaution

All nine commits in the last three months came from one contributor, giving the project a single-person maintenance dependency. Organization ownership partly mitigates handoff risk but does not remove it.

Repo popularitycaution

The repository has zero stars, forks, and watchers. For a package only 40 days old this is weak supporting evidence rather than a standalone abandonment concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy. This makes vulnerability reporting and response expectations less transparent, although it is not by itself evidence of unsafe code.