# microsoft/DynamicProto-JS — health index 70/100 (Good)

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

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 50/100 | Moderate |
| Community & Adoption | 18% | 70/100 | Good |
| Sustainability & Governance | 24% | 73/100 | Good |
| Engineering Quality | 20% | 84/100 | Good |
| Security | 16% | 74/100 | Good |
| AI Readiness | not counted | 42/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | Generates dynamic prototype methods for JavaScript objects (classes) by supporting method definition within their "class" constructor (like an instance version), this removes the need to expose internal properties on the instance (this) which results in better code minfication and therefore improved load times for your users. |
| Primary language | TypeScript |
| License | MIT |
| Stars | 28 |
| Forks | 13 |
| Created | 2019-11-06 |
| Last push | 2026-05-27 |
| Latest release | 1.1.11 |
| Commits (last year) | 30 |
| Bus factor | 1 |
| Topics | javascript, typescript, prototype, inheritence, microsoft, minification |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | @microsoft/dynamicproto-js | 2.0.5 | 7,525,138 |

## Vitality — 50/100 (Moderate)

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

### Development activity — 48/100 (At risk)

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

### Release discipline — 52/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 | 24 releases published |
| Release recency | not met | 0 / 36 | latest release 913 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~69.4 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 23.2 / 60 | 28 stars |
| Forks | partial | 9 / 25 | 13 forks |
| Watchers | partial | 5 / 15 | 9 watchers |

### Community health — 85/100 (Excellent)

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

### Ecosystem adoption (downloads) — 100/100 (Excellent)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | met | 80 / 80 | 7,525,138 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 73/100 (Good)

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) — 34/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 | partial | 8.1 / 13.5 | 6 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 3 contributing companies or organizations -- score normalized to 10 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 40.9 / 46.8 | 88% of issues closed |
| PR acceptance | partial | 36.5 / 38.2 | 82/86 decided PRs merged |
| OpenSSF Scorecard: Code-Review | met | 15 / 15 | all changesets reviewed |

### Ownership & stewardship — 80/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | met | 25 / 25 | 125,490 followers of microsoft |
| Track record | met | 25 / 25 | 8207 public repos, account ~12 yr old |

### Package maintenance — 100/100 (Excellent)

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

## Engineering Quality — 84/100 (Good)

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

### Engineering practices — 84/100 (Good)

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

### Documentation — 85/100 (Excellent)

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

## Security — 74/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 6 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | met | 2.5 / 2.5 | 14 out of 14 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 | met | 7.5 / 7.5 | all changesets reviewed |
| Contributors | met | 2.5 / 2.5 | project has 3 contributing companies or organizations -- score normalized to 10 |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| 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 | met | 7.5 / 7.5 | 19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 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 | partial | 3.5 / 5 | SAST tool detected but not run on all commits |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | met | 7.5 / 7.5 | 0 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:@microsoft/dynamicproto-js@2.0.5 runtime dependency closure — what installing the published package pulls in — 1 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 — 42/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 — 1/100 (Critical)

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

| 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 | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 54/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.json |
| Static type checking | met | 11 / 11 | lib/test/tsconfig.json, lib/tsconfig.json, rollup/test/tsconfig.json, rollup/tsconfig.json, tsconfig.json |
| Reproducible environment | not met | 0 / 10 | — |
| 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 — 94/100 (Excellent)

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

## Collection warnings

- Could not fetch npm package '@microsoft/dynamicproto-rollup' 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