in2code/lux

Repo bus factorcaution

One contributor made 21 of 22 recent commits, a 95.5% share, creating a concentrated continuity risk. A second contributor remains active and the repository is organization-owned, which provides some handoff capacity but does not eliminate the concentration concern.

Repo issue activitycaution

There are 7 open issues and 2 open pull requests, but no new or closed issues and no new or merged pull requests in the last month. The lack of recent issue-flow activity is a maintenance-transparency caution, though it is outweighed by recent commits and releases.

Repo toolingcaution

The repository uses make and Composer build tooling, supporting reproducible project operations, but no security scanning tools were detected. The missing scanning is a governance gap rather than evidence of abandonment.

Security policycaution

No repository security policy was found. This reduces transparency about vulnerability reporting and response procedures, although it does not by itself indicate unsafe code.

Token permissionscaution

Neither of the two analyzed workflows declares top-level token permissions. Although no workflow requests explicit top-level write access, the absence of least-privilege declarations leaves workflow permissions less constrained than ideal.