# idoknow/Campux — health index 67/100 (Moderate)

> Inspection of the public repository idoknow/Campux by inspect.software. It holds a health index of 67 out of 100, placing it in the Moderate 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/idoknow/Campux
- Report page: https://inspect.software/software/idoknow/Campux
- Full JSON report: https://inspect.software/api/repositories/idoknow/Campux/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/i/idoknow/Campux.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.16.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 75/100 | Good |
| Community & Adoption | 18% | 58/100 | Moderate |
| Sustainability & Governance | 24% | 59/100 | Moderate |
| Engineering Quality | 20% | 94/100 | Excellent |
| Security | 16% | 47/100 | At risk |
| AI Readiness | not counted | 75/100 | Good |

## Repository facts

| Field | Value |
|---|---|
| Description | “你一直在找的 QQ 校园墙自动化平台” ｜ 一键部署、自助开墙、自助投稿、网页审核、自动发说说、数据分析、多号管理｜万能墙、表白墙 自动化、QQ 空间、QQ 机器人、发说说 |
| Homepage | https://campux.top |
| Primary language | TypeScript |
| License | Apache-2.0 |
| Stars | 153 |
| Forks | 15 |
| Created | 2024-04-01 |
| Last push | 2026-07-19 |
| Latest release | v2.1.1 |
| Commits (last year) | 405 |
| Bus factor | 1 |
| Topics | qq, qzone |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/RockChinQ/Campux | v2.1.1+incompatible | — |

## Vitality — 75/100 (Good)

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

### Development activity — 74/100 (Good)

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

### Release discipline — 76/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 5 releases published |
| Release recency | met | 36 / 36 | latest release 10 days ago |
| Release cadence | partial | 12.6 / 27 | a release every ~168.9 days |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 58/100 (Moderate)

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

### Popularity & adoption — 47/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 35.4 / 60 | 153 stars |
| Forks | partial | 9.6 / 25 | 15 forks |
| Watchers | partial | 1.7 / 15 | 3 watchers |

### Community health — 70/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (Apache-2.0) |
| CONTRIBUTING guide | met | 18 / 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 — 59/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) — 42/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 9.4 / 22.5 | top contributor authored 58% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 12 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 11 contributing companies or organizations |

### Issue & PR responsiveness — 78/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 43.8 / 46.8 | 94% of issues closed |
| PR acceptance | partial | 34 / 38.2 | 81/91 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 2/29 approved changesets -- score normalized to 0 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 7.8 / 25 | 11 followers of idoknow |
| Track record | partial | 21 / 25 | 29 public repos, account ~5 yr old |

## Engineering Quality — 94/100 (Excellent)

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

### Engineering practices — 90/100 (Excellent)

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

### Documentation — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://campux.top |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 2 topics |
| Wiki | met | 10 / 10 | — |

## Security — 47/100 (At risk)

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 — 46/100 (At risk)

Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | excluded | 0 / 7.5 | internal 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 |
| CI-Tests | met | 2.5 / 2.5 | 8 out of 8 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 2/29 approved changesets -- score normalized to 0 |
| Contributors | met | 2.5 / 2.5 | project has 11 contributing companies or organizations |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | met | 5 / 5 | packaging workflow 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 | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | not met | 0 / 7.5 | 52 existing vulnerabilities detected |

### Dependency advisories — 51/100 (Moderate)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 254 resolved dependencies against OSV; 68 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.7 / 35 | 3 affected: golang.org/x/crypto v0.45.0 (critical 10.0), go.mongodb.org/mongo-driver v1.14.0 (moderate 6.5), github.com/redis/go-redis/v9 v9.5.5 (unknown) |
| 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 | 32.3 / 40 | 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 481 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 — 75/100 (Good)

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 — 75/100 (Good)

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | AGENTS.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 66/100 (Moderate)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc.js |
| Static type checking | met | 11 / 11 | apps/dash/tsconfig.json, apps/server/tsconfig.json, apps/web/tsconfig.json, legacy/frontend/jsconfig.json |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | partial | 53.6 / 55 | 7/283 source files over 60KB |

## Collection warnings

- go package 'github.com/RockChinQ/Campux' points at a different repository (https://github.com/RockChinQ/Campux); excluded from ecosystem scoring
- Could not fetch npm package 'campux-frontend' 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