# ssssssss-team/spider-flow — health index 25/100 (Critical)

> Inspection of the public repository ssssssss-team/spider-flow by inspect.software. It holds a health index of 25 out of 100, placing it in the Critical band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/ssssssss-team/spider-flow
- Report page: https://inspect.software/software/ssssssss-team/spider-flow
- Full JSON report: https://inspect.software/api/repositories/ssssssss-team/spider-flow/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/s/ssssssss-team/spider-flow.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.25.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 25/100 | Critical |
| Community & Adoption | 18% | 75/100 | Good |
| Sustainability & Governance | 24% | 52/100 | Moderate |
| Engineering Quality | 20% | 31/100 | At risk |
| Security | 16% | 24/100 | Critical |
| AI Readiness | not counted | 35/100 | At risk |

Abandonment Policy applies a 60% multiplier to weighted overall health and gives it a ceiling of 49.

## Repository facts

| Field | Value |
|---|---|
| Description | 新一代爬虫平台，以图形化方式定义爬虫流程，不写代码即可完成爬虫。 |
| Homepage | https://www.spiderflow.org |
| Primary language | Java |
| License | MIT |
| Stars | 11,348 |
| Forks | 2,175 |
| Created | 2020-03-27 |
| Last push | 2023-06-14 |
| Latest release | v0.5.0 |
| Commits (last year) | 0 |
| Bus factor | 1 |
| Topics | spider, crawler, jsoup, xpath, web-spider, webspider, webcrawler, web-crawler, spider-flow |

## Vitality — 25/100 (Critical)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | not met | 0 / 36 | last push 1132 days ago |
| Commit cadence | not met | 0 / 36 | 0/52 weeks with commits |
| Commit volume | not met | 0 / 18 | 0 commits in the last year |
| OpenSSF Scorecard: Maintained | not met | 0 / 10 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |

### Release discipline — 60/100 (Moderate)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 2 releases published |
| Release recency | not met | 0 / 36 | latest release 2290 days ago |
| Release cadence | met | 27 / 27 | a release every ~10.9 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | partial | 60 / 100 | no human commit for 1365 days; 5 unmet obligation(s): pull requests unanswered, issues unanswered, a fixed advisory left unapplied, releases stalled, Scorecard reports it unmaintained |

## Community & Adoption — 75/100 (Good)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 96/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | met | 60 / 60 | 11,348 stars |
| Forks | met | 25 / 25 | 2,175 forks |
| Watchers | partial | 11.1 / 15 | 99 watchers |

### Community health — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| CONTRIBUTING guide | not met | 0 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

## Sustainability & Governance — 52/100 (Moderate)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 30/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 7 / 22.5 | top contributor authored 69% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 18 contributors |
| OpenSSF Scorecard: Contributors | not met | 0 / 10 | project has 0 contributing companies or organizations -- score normalized to 0 |

### Issue & PR responsiveness — 69/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 35.3 / 46.8 | 76% of issues closed |
| PR acceptance | partial | 28 / 38.2 | 11/15 decided PRs merged |
| OpenSSF Scorecard: Code-Review | partial | 6 / 15 | Found 9/20 approved changesets -- score normalized to 4 |

### Ownership & stewardship — 63/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 14.9 / 25 | 119 followers of ssssssss-team |
| Track record | partial | 17.7 / 25 | 5 public repos, account ~6 yr old |

## Engineering Quality — 31/100 (At risk)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | not met | 0 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | not met | 0 / 20 | 0 out of 11 merged PRs checked by a CI test -- score normalized to 0 |

### Documentation — 75/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://www.spiderflow.org |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 9 topics |
| Wiki | met | 10 / 10 | — |

## Security — 24/100 (Critical)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 21/100 (Critical)

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | not met | 0 / 2.5 | 0 out of 11 merged PRs checked by a CI test -- score normalized to 0 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | partial | 3 / 7.5 | Found 9/20 approved changesets -- score normalized to 4 |
| Contributors | not met | 0 / 2.5 | project has 0 contributing companies or organizations -- score normalized to 0 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | not met | 0 / 5 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | partial | 3 / 7.5 | 6 existing vulnerabilities detected |

### Dependency advisories — 37/100 (At risk)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 10 resolved dependencies against OSV; 17 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | partial | 5 / 35 | 4 affected: org.apache.commons:commons-text 1.6 (critical 9.8), commons-io:commons-io 2.7 (high 7.5), org.jsoup:jsoup 1.11.3 (high 7.5), +1 more |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | partial | 22.8 / 40 | 4 advisory-carrying package(s) unaddressed past 90 days; oldest published 1944 days ago |

### Malicious dependencies — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 100/100 (Excellent)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 35/100 (At risk)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 7/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | partial | 6.9 / 40 | 13 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 34/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | pom.xml, spider-flow-api/pom.xml, spider-flow-core/pom.xml (toolchain convention, no task runner) |
| Automated tests | not met | 0 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | Java (statically typed) |
| Reproducible environment | met | 10 / 10 | Dockerfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

### Code legibility for models — 96/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Java (statically typed) |
| Manageable file sizes | partial | 51.5 / 55 | 10/155 source files over 60KB |

## Collection warnings

- Could not fetch maven package 'org.spiderflow:spider-flow-api' from its registry
- Could not fetch maven package 'org.spiderflow:spider-flow-web' from its registry
- Could not fetch maven package 'org.spiderflow:spider-flow-core' from its registry

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt