Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 14:50 UTC

steedos / cli

deploy and run your steedos apps

JavaScriptNo license detected★ 0 stars⑂ 0 forkssince Feb 2019archivedView on GitHub ↗
KindCommand-line toolLibraryhow this is determined

steedos/cli holds a health index of 11 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (69/100) and lowest on Vitality (1/100). The repository is archived, so no further maintenance is expected.

11
overall / 100
Critical

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.

11
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 33 is calibrated to 27 on the published index scale (record calibration 2026-08-02).

Ownership

SteedosOrganization
103 followers237 public repossince Dec 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmsteedos-cli3.0.148,6071,636117 days ago

Metrics by category

Vitality

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

1Critical · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 2,745 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push2,745
active_weeks_last_year0

Release discipline

1Critical
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0

Community & Adoption

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

26At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 2 watchers
Inputs used
forks0
stars0
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

66Good
How it's scored
52.5/80Monthly downloads — 8,607 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessteedos-cli
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads8,607
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?

69Good · 23% of overall

Maintainer resilience (bus factor)

23At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.3/22.5Commit distribution — top contributor authored 59% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.588

Issue & PR responsiveness

100Exceptional
How it's scored
42/42Issue resolution — 100% of issues closed
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs0
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

70Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
14.5/25Owner reach — 103 followers of steedos
25/25Track record — 237 public repos, account ~13 yr old
Inputs used
followers103
owner_typeOrganization
is_verifiedno
owner_loginsteedos
public_repos237
account_age_days5,010

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 117 days ago
20/20Version history — 1,636 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessteedos-cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish117

Engineering Quality

Are baseline engineering and documentation practices in place?

32At Risk · 19% of overall

Engineering practices

20At Risk
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

34At Risk · 16% of overall

Security posture

25At Risk
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — package-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestspackage.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

Dependency advisories

68Good
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
6.7/25Indirect dependencies free of known advisories — 3 affected: lodash 4.17.21 (high 8.1), tmp 0.0.33 (high 7.5), got 9.6.0 (moderate 5.3)
26.3/40No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,544 days ago
Inputs used
sourceosv
advisories6
affected_packages3
assessed_packages416
unassessed_packages0
affected_by_severityhigh 2, moderate 1
direct_affected_packages0
Matched the npm:steedos-cli@3.0.14 runtime dependency closure — what installing the published package pulls in — 416 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.

21At Risk · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.1/40Legible commit history — 1 of 48 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.021
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

23At Risk
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — .eslintrc
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 48
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/15 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes16,201
source_files_sampled15
oversized_source_files0

Key facts

0GitHub stars
2contributors
0commits, last 12 months
2,745days since last push
0releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/steedos/cli: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-10T14:50:11Z. Please include `D946:1FBC99:B88FA37:B342C25:6AA2C3A1` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@oclif/command^1.5.10package.json
npm@oclif/config^1.12.8package.json
npm@oclif/plugin-help^2.1.6package.json
npm@steedos/meteor-bundle-runner^1.0.9package.json
All dependencies 0

Full resolved dependency set from the GitHub dependency graph: 0 direct and 0 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Dependency advisories 3

Installing npm:steedos-cli@3.0.14 pulls in 416 packages, direct and transitive: 3 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
lodash4.17.21indirecthigh34.18.0
tmp0.0.33indirecthigh20.2.6
got9.6.0indirectmoderate112.1.0

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with steedos/cli. Read them side by side →

100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100coder/coderSecure environments for developers and their agentsExceptional100openai/openai-nodeOfficial JavaScript / TypeScript library for the OpenAI APIExceptional100mui/material-uiMaterial UI: Comprehensive React component library that implements Google's Material Design. Free forever.Exceptional100ionic-team/ionic-frameworkA powerful cross-platform UI toolkit for building native-quality iOS, Android, and Progressive Web Apps with HTML, CSS, and JavaScript.Exceptional100Arize-ai/phoenixAI Observability & EvaluationExceptional

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 statistics — npm.