jupitern/slimcore

This release is usable but presents meaningful maintenance and transparency concerns. The package has a clear MIT license, stable releases, 16 releases over 480 days, recent publication activity, no deprecation, and no install-time lifecycle scripts. However, the linked personal repository has no commits or active maintainers in the last 3 months, no tests or changelog, no security scanning or security policy, and negligible adoption signals. The repository was pushed very recently and the release cadence is steady, which partially offsets the inactivity concern, but the thin project infrastructure and single-person backing make this a dependency to adopt with caution.

Latest 4.4.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health checks

Dependency profile

The package has five runtime dependencies and no dev dependencies. The dependency set is moderate, but the absence of dev dependencies also aligns with the absence of repository tests and reduces evidence of development validation.

Package scaffolding

The artifact and repository contain only a very short README and no tests or changelog; the repository's GitHub Releases provide some release transparency but do not compensate for the lack of validation and documentation.

Project backing

The repository is owned by a user rather than an organization, indicating a relatively thin backing model. This matters more given the lack of recent commits and external popularity signals.

Repo commit activity

The repository records 0 commits and 0 active maintainers in the last 3 months, a material maintenance concern. The very recent repository push and steady release history partly offset this, so the signal is caution rather than danger.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently negative for a small package, but it provides no evidence of an active user or contributor feedback loop.