# meshery-extensions/meshery-extensions-packages — health index 68/100 (Moderate)

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

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 100/100 | Excellent |
| Community & Adoption | 18% | 63/100 | Moderate |
| Sustainability & Governance | 24% | 54/100 | Moderate |
| Engineering Quality | 20% | 56/100 | Moderate |
| Security | 16% | 64/100 | Moderate |
| AI Readiness | not counted | 47/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | Public registry for Meshery remote provider packages |
| Homepage | https://cloud.meshery.io |
| Primary language | HTML |
| License | Apache-2.0 |
| Stars | 61 |
| Forks | 82 |
| Created | 2020-12-22 |
| Last push | 2026-07-24 |
| Latest release | v1.0.62-1 |
| Commits (last year) | 31,124 |
| Bus factor | 1 |
| Topics | meshery, meshery-provider, meshery-remote-provider, meshery-extensions, meshery-plugins, hacktoberfest |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | @layer5/meshery-design-embed | 0.6.0 | 12,927 |

## Vitality — 100/100 (Excellent)

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

### Development activity — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 1 days ago |
| Commit cadence | met | 36 / 36 | 52/52 weeks with commits |
| Commit volume | met | 18 / 18 | 31124 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 100 releases published |
| Release recency | met | 36 / 36 | latest release 4 days ago |
| Release cadence | met | 27 / 27 | a release every ~1.8 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 1 days ago |

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

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

### Popularity & adoption — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 28.8 / 60 | 61 stars |
| Forks | partial | 15.9 / 25 | 82 forks |
| Watchers | partial | 5 / 15 | 9 watchers |

### Community health — 77/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 | met | 6.3 / 6.3 | — |

## Sustainability & Governance — 54/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) — 25/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 0.4 / 22.5 | top contributor authored 98% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 79 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 86/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 38.5 / 46.8 | 82% of issues closed |
| PR acceptance | partial | 34.5 / 38.2 | 582/645 decided PRs merged |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 12.8 / 25 | 60 followers of meshery-extensions |
| Track record | partial | 13.4 / 25 | 27 public repos, account ~1 yr old |

## Engineering Quality — 56/100 (Moderate)

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

### Engineering practices — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 23 workflow(s) |
| Tests present | not met | 0 / 24 | — |
| Linter config | met | 16 / 16 | .eslintrc.cjs |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 65/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://cloud.meshery.io |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 6 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 64/100 (Moderate)

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 — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | met | 30 / 30 | — |
| Dependabot config | not met | 0 / 25 | — |
| Dependency lockfiles | met | 25 / 25 | package-lock.json |
| CodeQL workflow | not met | 0 / 20 | — |

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

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 292 resolved dependencies against OSV. 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 | met | 35 / 35 | no direct dependency carries a known advisory |
| 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 | 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 — 47/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 — 73/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | not met | 0 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc.cjs |
| Static type checking | not met | 0 / 11 | — |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | partial | 2 / 10 | 1 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 49/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | HTML without a type-check config |
| Manageable file sizes | partial | 48.9 / 55 | 1/9 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- npm package '@layer5/meshery-design-embed' points at a different repository (https://github.com/layer5labs/meshery-extensions-packages); excluded from ecosystem scoring
- OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

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