# remotemerge/nepali-date-converter — health index 59/100 (Moderate)

> Inspection of the public repository remotemerge/nepali-date-converter by inspect.software. It holds a health index of 59 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/remotemerge/nepali-date-converter
- Report page: https://inspect.software/software/remotemerge/nepali-date-converter
- Full JSON report: https://inspect.software/api/repositories/remotemerge/nepali-date-converter/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/r/remotemerge/nepali-date-converter.svg
- Inspected: 2026-09-17
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 73/100 | Good |
| Community & Adoption | 17% | 40/100 | Weak |
| Sustainability & Governance | 23% | 41/100 | Weak |
| Engineering Quality | 19% | 70/100 | Good |
| Security | 16% | 56/100 | Moderate |
| AI Readiness | 4% | 44/100 | Weak |

The weighted overall 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | A modern JavaScript library for seamless conversion between Bikram Sambat (BS) and Gregorian (AD) dates. Easily convert Nepali dates to English dates and vice versa with support for years 1975 BS to 2099 BS. |
| Classification | library |
| Homepage | https://www.npmjs.com/package/@remotemerge/nepali-date-converter |
| Primary language | TypeScript |
| License | MIT |
| Stars | 6 |
| Forks | 4 |
| Created | 2022-09-25 |
| Last push | 2026-09-12 |
| Latest release | 1.2.1 |
| Commits (last year) | 72 |
| Bus factor | 1 |
| Topics | ad-to-bs, bikram-sambat, bs-to-ad, date-conversion, nepali-calendar, nepali-date, nepali-date-converter, nepali-miti, miti-pariwartan, nepali-date-formatter, nepali-date-library, nepali-date-tool, nepali-date-utility |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | @remotemerge/nepali-date-converter | 1.2.1 | 8,002 |

## Vitality — 73/100 (Good)

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

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 4 releases published |
| Release recency | met | 36 / 36 | latest release 52 days ago |
| Release cadence | partial | 12.6 / 27 | a release every ~189.4 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Exceptional)

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

## Community & Adoption — 40/100 (Weak)

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

### Popularity & adoption — 15/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 11.3 / 60 | 6 stars |
| Forks | partial | 4 / 25 | 4 forks |
| Watchers | not met | 0 / 15 | 1 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) — 65/100 (Good)

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

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

## Sustainability & Governance — 41/100 (Weak)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% 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 — 25/100 (At Risk)

Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 42 | no issues or no data |
| PR acceptance | partial | 11.1 / 30 | 17/46 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/3 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 55/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 | 14.8 / 25 | 113 followers of remotemerge |
| Track record | partial | 18.9 / 25 | 8 public repos, account ~13 yr old |

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

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

## Engineering Quality — 70/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 3 workflow(s) |
| Tests present | met | 24 / 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 | met | 20 / 20 | 3 out of 3 merged PRs checked by a CI test -- score normalized to 10 |

### Documentation — 65/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://www.npmjs.com/package/@remotemerge/nepali-date-converter |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 13 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 56/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 — 56/100 (Moderate)

Excluded from scoring (no data or not applicable): Signed-Releases. 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 | met | 2.5 / 2.5 | 3 out of 3 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 0/3 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 | 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 0 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | partial | 2.5 / 5 | dependency not pinned by hash detected -- score normalized to 5 |
| SAST | partial | 2.5 / 5 | SAST tool is not run on all commits -- score normalized to 5 |
| Security-Policy | not met | 0 / 5 | security policy file not 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 | partial | 6.8 / 7.5 | 1 existing vulnerabilities detected |

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

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 — 44/100 (Weak)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 4/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 | 3.7 / 40 | 7 of 100 human commits state their intent (structured subject or explanatory body) |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | html/tsconfig.json |
| Reproducible environment | met | 10 / 10 | Dockerfile |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | partial | 5 / 8 | dependency automation configured, none observed in the sampled commits |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 5 / 10 | dependency not pinned by hash detected -- score normalized to 5 |

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

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

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- No resolved dependencies carried a version and a supported ecosystem

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