Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 10:46 UTC

mazira / rtf-stream-parser

Contains native Node classes for transforming an RTF byte stream into tokens, and de-encapsulating HTML

TypeScriptMIT★ 26 stars⑂ 4 forkssince Jun 2016View on GitHub ↗

mazira/rtf-stream-parser holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on AI Readiness (56/100) and lowest on Vitality (35/100). It was last updated 35 days ago. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

41
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

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

Ownership

Mazira, LLCOrganization
1 follower15 public repossince Aug 2011

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmrtf-stream-parser4.0.0222,6852435 days agortfparserrichtextrichtextdeencapsulatorde-encapsulatordeencapsultede-encapsulateencapsulatorencapsulateoutlook

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

35Weak · 21% of overall
How it's scored
18/36Push recency — last push 35 days ago
1.4/36Commit cadence — 2/52 weeks with commits
8.1/18Commit volume — 7 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year7
human_commit_share1
days_since_last_push35
active_weeks_last_year2
How it's scored
16.2/27Ships releases — 7 version tags (no GitHub releases)
0/36Release recency — latest release 1,497 days ago
19.8/27Release cadence — a release every ~94 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv3.6.0
releases_from_tagsyes
days_since_latest_release1,497
mean_days_between_releases94
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

51Moderate · 17% of overall
How it's scored
22.7/60Stars — 26 stars
4/25Forks — 4 forks
1.7/15Watchers — 3 watchers
Inputs used
forks4
stars26
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
71.3/80Monthly downloads — 222,685 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesrtf-stream-parser
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads222,685
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

45Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
26.7/42Issue resolution — 64% of issues closed
0/30PR acceptance — 0/2 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues4
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.636
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of mazira
20.8/25Track record — 15 public repos, account ~15 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginmazira
public_repos15
account_age_days5,501

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 35 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesrtf-stream-parser
ecosystemsnpm
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate2
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories22
affected_packages7
assessed_packages206
unassessed_packages0
affected_by_severityhigh 6, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 206 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.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
4.6/40Legible commit history — 5 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.086
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 58
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/36 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes59,095
source_files_sampled36
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

26GitHub stars
1contributors
7commits, last 12 months
35days since last push
7releases
1bus factor
4open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
7Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

1223344412017-102020-122024-01
Major 0Minor 3Patch 4

Each point covers 6 days.

OpenSSF Scorecard 2.0 / 10
2.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-15 10:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities21 existing vulnerabilities detected
All dependencies 206

Full resolved dependency set from the GitHub dependency graph: 0 direct and 206 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@babel/code-frame7.12.11indirect
npm@babel/helper-validator-identifier7.12.11indirect
npm@babel/highlight7.13.10indirect
npm@eslint/eslintrc0.4.0indirect
npm@nodelib/fs.scandir2.1.4indirect
npm@nodelib/fs.stat2.0.4indirect
npm@nodelib/fs.walk1.2.6indirect
npm@types/chai4.2.16indirect
npm@types/chai-as-promised7.1.3indirect
npm@types/json-schema7.0.7indirect
npm@types/mocha8.2.2indirect
npm@types/node12.20.10indirect
npm@typescript-eslint/eslint-plugin4.22.0indirect
npm@typescript-eslint/experimental-utils4.22.0indirect
npm@typescript-eslint/parser4.22.0indirect
npm@typescript-eslint/scope-manager4.22.0indirect
npm@typescript-eslint/types4.22.0indirect
npm@typescript-eslint/typescript-estree4.22.0indirect
npm@typescript-eslint/visitor-keys4.22.0indirect
npm@ungap/promise-all-settled1.1.2indirect
npmacorn7.4.1indirect
npmacorn-jsx5.3.1indirect
npmajv6.15.0indirect
npmajv8.20.0indirect
npmansi-colors4.1.1indirect
npmansi-regex3.0.1indirect
npmansi-regex5.0.1indirect
npmansi-styles3.2.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.2indirect
npmargparse1.0.10indirect
npmargparse2.0.1indirect
npmarray-union2.1.0indirect
npmassertion-error1.1.0indirect
npmastral-regex2.0.0indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion1.1.18indirect
npmbraces3.0.3indirect
npmbrowser-stdout1.3.1indirect
npmcallsites3.1.0indirect
npmcamelcase6.2.0indirect
npmchai4.3.4indirect
npmchai-as-promised7.1.1indirect
npmchalk2.4.2indirect
npmchalk4.1.1indirect
npmcheck-error1.0.2indirect
npmchokidar3.5.1indirect
npmcliui7.0.4indirect
npmcolor-convert1.9.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.3.1indirect
npmdecamelize4.0.0indirect
npmdeep-eql3.0.1indirect
npmdeep-is0.1.3indirect
npmdiff5.0.0indirect
npmdir-glob3.0.1indirect
npmdoctrine3.0.0indirect
npmemoji-regex8.0.0indirect
npmenquirer2.3.6indirect
npmescalade3.1.1indirect
npmescape-string-regexp1.0.5indirect
npmescape-string-regexp4.0.0indirect
npmeslint7.25.0indirect
npmeslint-scope5.1.1indirect
npmeslint-utils2.1.0indirect
npmeslint-visitor-keys1.3.0indirect
npmeslint-visitor-keys2.0.0indirect
npmespree7.3.1indirect
npmesprima4.0.1indirect
npmesquery1.4.0indirect
npmesrecurse4.3.0indirect
npmestraverse4.3.0indirect
npmestraverse5.2.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-glob3.2.5indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfast-uri3.1.5indirect
npmfastq1.11.0indirect
npmfile-entry-cache6.0.1indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmflat-cache3.0.4indirect
npmflatted3.4.4indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmfunctional-red-black-tree1.0.1indirect
npmget-caller-file2.0.5indirect
npmget-func-name2.0.2indirect
npmglob7.1.6indirect
npmglob-parent5.1.2indirect
npmglobals12.4.0indirect
npmglobals13.8.0indirect
npmglobby11.0.3indirect
npmgrowl1.10.5indirect
npmhas-flag3.0.0indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmiconv-lite0.6.2indirect
npmignore4.0.6indirect
npmignore5.1.8indirect
npmimport-fresh3.3.0indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point2.0.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.1indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmisexe2.0.0indirect
npmjs-tokens4.0.0indirect
npmjs-yaml3.15.1indirect
npmjs-yaml4.0.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-schema-traverse1.0.0indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash4.18.1indirect
npmlodash.clonedeep4.5.0indirect
npmlodash.flatten4.4.0indirect
npmlodash.truncate4.4.2indirect
npmlog-symbols4.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmminimatch3.0.4indirect
npmmocha8.4.0indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmnanoid3.1.20indirect
npmnatural-compare1.4.0indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmoptionator0.9.1indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-type4.0.0indirect
npmpathval1.1.1indirect
npmpicomatch2.3.2indirect
npmprelude-ls1.2.1indirect
npmprogress2.0.3indirect
npmpunycode2.1.1indirect
npmqueue-microtask1.2.3indirect
npmrandombytes2.1.0indirect
npmreaddirp3.5.0indirect
npmregexpp3.1.0indirect
npmrequire-directory2.1.1indirect
npmrequire-from-string2.0.2indirect
npmresolve-from4.0.0indirect
npmreusify1.0.4indirect
npmrimraf3.0.2indirect
npmrun-parallel1.2.0indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsemver7.8.5indirect
npmserialize-javascript5.0.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmslash3.0.0indirect
npmslice-ansi4.0.0indirect
npmsprintf-js1.0.3indirect
npmstring-width2.1.1indirect
npmstring-width4.2.2indirect
npmstrip-ansi4.0.0indirect
npmstrip-ansi6.0.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color5.5.0indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtable6.5.1indirect
npmtext-table0.2.0indirect
npmto-regex-range5.0.1indirect
npmtslib1.14.1indirect
npmtsutils3.21.0indirect
npmtype-check0.4.0indirect
npmtype-detect4.0.8indirect
npmtype-fest0.20.2indirect
npmtype-fest0.8.1indirect
npmtypescript4.2.4indirect
npmuri-js4.4.1indirect
npmv8-compile-cache2.3.0indirect
npmwhich2.0.2indirect
npmwide-align1.1.3indirect
npmword-wrap1.2.5indirect
npmworkerpool6.1.0indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.4indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 206 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
fast-uri3.1.5indirecthigh44.1.3
js-yaml3.15.1indirecthigh14.3.2
js-yaml4.0.0indirecthigh54.3.2
minimatch3.0.4indirecthigh410.2.3
nanoid3.1.20indirecthigh55.1.16
serialize-javascript5.0.1indirecthigh27.0.5
diff5.0.0indirectmoderate18.0.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.