secondnetwork/blade-tabler-icons

Project backingcaution

The repository is owned by a user account rather than an organization, and recent activity is concentrated in one contributor. That offers less formal handoff capacity than organization-backed maintenance.

Repo bus factorcaution

All three recent commits came from one contributor, giving the project a single-person operational dependency. The ongoing release history partly compensates, but it does not remove the continuity risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. For a package with active automated releases, that is a modest security-maintenance gap.

Security policycaution

The repository has no security policy. This makes vulnerability reporting and response expectations less transparent, though it does not indicate abandonment on its own.

Workflow auditcaution

All nine analyzed action references are unpinned, and two workflows grant top-level write access, creating avoidable workflow supply-chain and token-scope risk. The audit analyzed all three workflows and found no untrusted checkout, script injection, or other reported findings.