# fjc0k/mounted — health index 19/100 (Critical)

> Inspection of the public repository fjc0k/mounted by inspect.software. It holds a health index of 19 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/fjc0k/mounted
- Report page: https://inspect.software/software/fjc0k/mounted
- Full JSON report: https://inspect.software/api/repositories/fjc0k/mounted/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/f/fjc0k/mounted.svg
- Inspected: 2026-07-23
- Methodology: metrics 1.13.0, report schema 0.27.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 20/100 | Critical |
| Community & Adoption | 18% | 42/100 | At risk |
| Sustainability & Governance | 24% | 33/100 | At risk |
| Engineering Quality | 20% | 35/100 | At risk |
| Security | 16% | 32/100 | At risk |
| AI Readiness | not counted | 43/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 | 基于 Taro 的小程序组件库。 |
| Homepage | https://npm.im/mounted |
| Primary language | TypeScript |
| License | MIT |
| Stars | 67 |
| Forks | 8 |
| Created | 2019-01-26 |
| Last push | 2020-06-06 |
| Latest release | v1.6.1 |
| Commits (last year) | 0 |
| Bus factor | 1 |
| Topics | taro, taro-components, weapp, weapp-components |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | mounted | 1.6.1 | 153 |

## Vitality — 20/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 2237 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 — 48/100 (At risk)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | partial | 16.2 / 27 | 43 version tags (no GitHub releases) |
| Release recency | not met | 0 / 36 | latest release 2476 days ago |
| Release cadence | met | 27 / 27 | a release every ~4.8 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 2476 days; 3 unmet obligation(s): pull requests unanswered, releases stalled, Scorecard reports it unmaintained |

## Community & Adoption — 42/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 29.5 / 60 | 67 stars |
| Forks | partial | 7 / 25 | 8 forks |
| Watchers | partial | 2.7 / 15 | 4 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 | — |

### Ecosystem adoption (downloads) — 36/100 (At risk)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 29.2 / 80 | 153 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 33/100 (At risk)

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) — 10/100 (Critical)

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

### Issue & PR responsiveness — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | not met | 0 / 46.8 | 0% of issues closed |
| PR acceptance | not met | 0 / 38.2 | 0/1 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

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

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 16.8 / 25 | 213 followers of fjc0k |
| Track record | met | 25 / 25 | 126 public repos, account ~11 yr old |

### Package maintenance — 69/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on npm |
| Publish recency | partial | 4 / 35 | latest publish 2476 days ago |
| Version history | met | 20 / 20 | 47 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

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

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

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

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

| 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 | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | no pull request found |

### 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://npm.im/mounted |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 4 topics |
| Wiki | met | 10 / 10 | — |

## Security — 32/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 — 15/100 (Critical)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, 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 | excluded | 0 / 2.5 | no pull request found |
| 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 0/30 approved changesets -- score normalized to 0 |
| 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 | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | no SAST tool detected |
| 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 | not met | 0 / 7.5 | 207 existing vulnerabilities detected |

### Dependency advisories — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:mounted@1.6.1 runtime dependency closure — what installing the published package pulls in — 6 packages. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | met | 25 / 25 | no indirect dependency carries a known advisory |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### 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 — 43/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 — 40/100 (At risk)

| 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 | met | 40 / 40 | 100 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 23/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | not met | 0 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| 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 | excluded | 0 / 10 | no dependencies found |

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

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

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

## 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