codger/es6

Its MIT licensing and matching repository make the package transparent to inspect. The project has little adoption, no security policy, and no recent commits, so future maintenance is uncertain.

Latest 0.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases since October 2018, with no releases in the last 12 months and a median interval of about 6 years 4 months. This indicates a very slow maintenance cadence.

Repo commit activity

There were no commits and no active maintainers in the three months measured. Combined with the sparse release history, this raises uncertainty about ongoing maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher, showing very limited visible adoption. Popularity is supporting evidence rather than a verdict, so this is a modest concern.

Repo tooling

The repository uses Composer build tooling, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than evidence of abandonment.

Security policy

No repository security policy was found. This weakens disclosure transparency, although it does not by itself indicate that the package is unsafe to depend on.