hsldymq/byte-order-op

The repository has no security policy, and its workflow uses all four actions without pinning them to fixed versions. Tests, documentation, licensing, and a matching source repository provide useful protection despite the long maintenance gap.

Latest v0.1.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about four years: only three releases overall and none in the last 12 months. That materially raises abandonment risk for a dependency, although the package is small and its latest release has supporting documentation.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is strong evidence that maintenance capacity is currently absent.

Repo popularity

The repository has zero stars and forks and one watcher, so there is little visible community support if maintenance stops. Popularity is only supporting evidence, but it reinforces the maintenance concern.

Security policy

No security policy is present in the linked repository. This weakens the project's transparency and gives users no documented route for reporting vulnerabilities.

Workflow audit

The single workflow was fully analyzed with no detected dangerous sinks or audit findings, but all four action references are unpinned. That leaves build inputs exposed to upstream action changes and is a modest supply-chain hygiene gap.