Package Health

tempcord/framework

Tempcord/framework appears suitable for adoption, with strong evidence of active early-stage development and reasonable project transparency. It has 17 releases in 14 days, a stable non-prerelease v1.3.0, recent repository activity, 50 commits from three active contributors, 16 merged pull requests, documented source structure, tests in the repository, a changelog, an MIT license, Dependabot, and no deprecation or archive status. The main reservations are that the project is very young, has no packaged tests, has no security policy, shows zero popularity metrics, and has some GitHub Actions permission and pull_request_target exposure; these warrant review before using it in a critical production dependency, but do not by themselves make it unfit.

Latest v1.3.0PackagistPackagist

78%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

100

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

89

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

70

Health Score Breakdown

Dangerous workflowscaution

One workflow uses pull_request_target, which deserves review because that trigger can expose privileged workflow context, but no untrusted checkout or script-injection patterns were detected.

Release historycaution

The package is only 14 days old, which limits evidence of long-term stability, although 17 releases and a latest release on the collection date show active development.

Repo popularitycaution

The repository has zero stars, forks, and watchers, so there is little external adoption evidence; this is supporting evidence only and is partly explained by the package's 14-day age.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.

Token permissionscaution

Two workflows lack top-level permissions and the release workflow grants top-level write access, creating avoidable CI privilege concerns even though one workflow is explicitly read-only.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

CyberWolf.Studio

Direct Dependencies

DependencyLast ReleaseScore
tempest/log
Version ^3.18
tempest/core
Version ^3.18
tempest/console
Version ^3.18
tempest/database
Version ^3.18
tempest/event-bus
Version ^3.18

Weekly Downloads

Info

Last Published
11 days ago
Created
25 days ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform