Package Health

martinjuul/duckdb

Documentation, tests, release notes, and licensing give consumers a clear and well-supported package. The missing security policy and automated security scanning leave avoidable maintenance gaps.

Latest 1.3.1PackagistPackagist

68%

Total Score

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

67

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

88

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

67

Health Score Breakdown

Project backingcaution

The repository is owned by an individual rather than an organization, so the single-contributor maintenance concentration is not visibly backed by a larger team.

Release historycaution

Seven releases were published within about one day, showing active delivery but providing little evidence of long-term project maturity yet.

Repo bus factorcaution

All 123 recent commits came from one contributor, so maintenance depends heavily on a single person despite the high activity level.

Repo toolingcaution

The project uses CMake and Composer, but no security-scanning tools were detected, leaving security maintenance less visible.

Security policycaution

The repository has no security policy, so its vulnerability reporting and response process is not documented.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Martin Juul Christiansen

Direct Dependencies

No direct dependencies.

Weekly Downloads

Info

Last Published
18 hours ago
Created
14 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