Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-24 06:23 UTC

felores / kie-cli-mcp

Kie.ai CLI + MCP Server: Cost efficient media API ready to be used by MCP clients like Claude, Codex, OpenCode or Pi. Generative Ai Models available: Nano Banana Pro, Veo3 , Runway Aleph, Suno V5.5, ElevenLabs, Seedance 2.5, Seedream, Qwen, Flux, Wan, Midjourney and OpenAI Image 2

TypeScriptMIT★ 76 stars⑂ 15 forkssince Oct 2025forkView on GitHub ↗
KindCommand-line toolNetwork serviceMCP serverLibraryhow this is determined

felores/kie-cli-mcp holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (40/100). It was last updated 29 days ago. A single contributor accounts for most of its recent work.

65
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

65
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

Felo RestrepoPersonal account
37 followers51 public repossince Nov 2018Markenetica

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

80Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
10.4/36Commit cadence15/52 weeks with commits
18/18Commit volume151 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year151
human_commit_share1
days_since_last_push29
active_weeks_last_year15

Release discipline

100Exceptional
How it's scored
27/27Ships releases47 releases published
36/36Release recencylatest release 29 days ago
27/27Release cadencea release every ~8.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count47
latest_release_tagv0.6.1
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases8.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

40Weak · 17% of overall
How it's scored
30.4/60Stars76 stars
9.6/25Forks15 forks
0/15Watchers1 watchers
Inputs used
forks15
stars76
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
49.1/80Monthly downloads4,787 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@felores/kie-cli, @felores/kie-ai-mcp-server, @felores/kie-ai-openai-server
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,787
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

51Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.9/22.5Commit distributiontop contributor authored 96% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.962
How it's scored
21/42Issue resolution50% of issues closed
24.8/30PR acceptance33/40 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs33
open_issues2
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.5
closed_unmerged_prs7
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.4/25Owner reach37 followers of felores
24.5/25Track record51 public repos, account ~7 yr old
Inputs used
followers37
owner_typeUser
is_verified
owner_loginfelores
public_repos51
account_age_days2,881
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on npm
35/35Publish recencylatest publish 29 days ago
20/20Version history47 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@felores/kie-cli, @felores/kie-ai-mcp-server, @felores/kie-ai-openai-server
ecosystemsnpm
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/@felores/kie-ai-mcp-server
0/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsai, image-generation, mcp, model-context-protocol, nano-banana, typescript, veo3, video-generation, kie-ai
has_wikiyes
homepagehttps://www.npmjs.com/package/@felores/kie-ai-mcp-server
docs_sitehttps://www.npmjs.com/package/@felores/kie-ai-mcp-server
has_readmeno
has_docs_diryes
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities48 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
6.8/25Indirect dependencies free of known advisories2 affected: tar 6.2.1 (high 8.8), @tootallnate/once 1.1.2 (low 3.3)
30.7/40No advisories left outstanding2 advisory-carrying package(s) unaddressed past 90 days; oldest published 250 days ago
Inputs used
sourceosv
advisories13
affected_packages2
assessed_packages133
unassessed_packages0
affected_by_severityhigh 1, low 1
direct_affected_packages0
Matched the npm:@felores/kie-cli@0.8.0 runtime dependency closure — what installing the published package pulls in — 133 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

75Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md, docs/AGENTS.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.kie.ai/llms.txt)
40/40Legible commit history93 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.kie.ai/llms.txt
legible_history_share0.93
agent_instruction_filesAGENTS.md, CLAUDE.md, docs/AGENTS.md
agent_instruction_max_bytes31,421
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingpackages/cli/tsconfig.json, packages/core/tsconfig.json, packages/mcp/tsconfig.json, packages/openai/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice23 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/cli/tsconfig.json, packages/core/tsconfig.json, packages/mcp/tsconfig.json, packages/openai/tsconfig.json
agent_commit_share0.23
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.1/55Manageable file sizes2/123 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes69,459
source_files_sampled123
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

76GitHub stars
3contributors
151commits, last 12 months
29days since last push
47releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
22Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

03581013151522025-112026-042026-09
Major 3Minor 9Patch 10
OpenSSF Scorecard 4.1 / 10
4.1aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-24 06:23 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities48 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npmsqlite3^5.1.6packages/cli/package.json
npmyargs^17.7.2packages/cli/package.json
npmzod^4.4.3packages/cli/package.json
npmsqlite3^5.1.6packages/core/package.json
npmzod^4.4.3packages/core/package.json
npm@modelcontextprotocol/node^2.0.0packages/mcp/package.json
npm@modelcontextprotocol/server^2.0.0packages/mcp/package.json
npmexpress^4.21.2packages/mcp/package.json
npmsqlite3^5.1.6packages/mcp/package.json
npmzod^4.4.3packages/mcp/package.json
npm@types/express^4.17.21packages/openai/package.json
npmexpress^4.21.2packages/openai/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 2

Installing npm:@felores/kie-cli@0.8.0 pulls in 133 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tar6.2.1indirecthigh127.5.21
@tootallnate/once1.1.2indirectlow13.0.1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.