bigcommerce/injector

bigcommerce/injector 5.0.8 appears to be a healthy, mature dependency: it has existed since 2016, has 31 releases including 8 in the last 12 months, is stable and not deprecated, and is backed by a matching, active BigCommerce organization repository. The package and repository include tests, a complete file tree, MIT licensing, and no install-time lifecycle scripts. The main concerns are that only one contributor made the two commits in the last three months, repository popularity is modest, and no security policy or security-scanning tooling was observed; these warrant monitoring but do not outweigh the strong release history and organizational backing.

Latest 5.0.8

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All two recent commits came from one contributor, producing a concentrated recent bus factor; organizational ownership partly mitigates succession risk but does not eliminate it.

Repo commit activity

There were two commits in the last three months, so activity has not stopped, but the volume is modest and should be monitored for continued momentum.

Repo popularity

The repository has only 2 stars and 6 forks, indicating limited public adoption evidence; popularity is supporting evidence, so this is a modest concern rather than a health verdict.

Repo tooling

Composer build tooling is present, but no security-scanning tools were observed, leaving a security-hygiene gap that is relevant but not independently severe.

Security policy

The repository has no security policy, which reduces transparency about vulnerability reporting and response procedures.