Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 14:31 UTC

redis / redis-om-node

Object mapping, and more, for Redis and Node.js. Written in TypeScript.

TypeScriptMIT★ 1,256 stars⑂ 87 forkssince Sep 2021View on GitHub ↗

redis/redis-om-node holds a health index of 32 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (71/100) and lowest on Vitality (20/100). It was last updated 527 days ago. A single contributor accounts for most of its recent work.

overall / 100

At Risk

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.

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)

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 53 is calibrated to 54 on the published index scale (record calibration 2026-08-02).

Ownership

RedisOrganization · verified domain

2,958 followers79 public repossince Mar 2012

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	redis-om	0.4.7	126,124	30	693 days ago	redis orm

Metrics by category

Vitality

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

20At Risk · 21% of overall

Development activity

1Critical

Abandonment alert

Work has arrived and nobody has attended to it

no human commit in 527 daysautomated commits excludedpull requests left unansweredissues left unansweredreleases stalledOpenSSF Scorecard reports it unmaintainedOverall rating: At Risk ceiling

Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.

How abandonment is assessed

How it's scored

0/36	Push recency — last push 527 days ago
0/36	Commit cadence — 0/52 weeks with commits
0/18	Commit volume — 0 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	0
human_commit_share	1
days_since_last_push	527
active_weeks_last_year	0

Release discipline

48Weak

How it's scored

16.2/27	Ships releases — 6 version tags (no GitHub releases)
0/36	Release recency — latest release 1,665 days ago
27/27	Release cadence — a release every ~14 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	6
latest_release_tag	v0.2.0
releases_from_tags	yes
days_since_latest_release	1,665
mean_days_between_releases	14

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?

68Good · 17% of overall

Popularity & adoption

74Good

How it's scored

50.3/60	Stars — 1,256 stars
16.1/25	Forks — 87 forks
7.9/15	Watchers — 27 watchers

Inputs used

forks	87
stars	1,256
watchers	27
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

85Excellent

How it's scored

68/80	Monthly downloads — 126,124 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	redis-om
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	126,124
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?

71Good · 23% of overall

Maintainer resilience (bus factor)

37Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
4.3/22.5	Commit distribution — top contributor authored 81% of commits
13.5/13.5	Contributor breadth — 25 contributors
10/10	OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	25
top_contributor_share	0.808

Issue & PR responsiveness

78Good

How it's scored

27.8/42	Issue resolution — 66% of issues closed
25.4/30	PR acceptance — 83/98 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	83
open_issues	56
closed_issues	110
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.663
closed_unmerged_prs	15
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

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

Ownership & stewardship

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
25/25	Owner reach — 2,958 followers of redis
25/25	Track record — 79 public repos, account ~14 yr old

Inputs used

followers	2,958
owner_type	Organization
is_verified	yes
owner_login	redis
public_repos	79
account_age_days	5,302

Package maintenance

79Good

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
14/35	Publish recency — latest publish 693 days ago
20/20	Version history — 30 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	redis-om
ecosystems	npm
any_deprecated	no
min_days_since_publish	693

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall

Engineering practices

48Weak

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
25/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

49Weak · 16% of overall

Security posture

36Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
0/2.5	CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
2.5/2.5	Contributors — project has 4 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
1/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 47 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	3.6

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

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	16
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:redis-om@0.4.7 runtime dependency closure — what installing the published package pulls in — 16 packages. 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.

50Moderate · 4% of overall

Agent context & guidance

33At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15	Machine-readable docs (llms.txt) — llms.txt served by the project website (https://redis.io/llms.txt)
18.1/40	Legible commit history — 34 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	yes
llms_txt_url	https://redis.io/llms.txt
legible_history_share	0.34
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

45Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
2/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	yes
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
55/55	Manageable file sizes — 0/143 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	26,014
source_files_sampled	143
oversized_source_files	0

Key facts

1,256GitHub stars

25contributors

0commits, last 12 months

527days since last push

6releases

1bus factor

56open 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 ★ / 87 ⇿

0Stars

87Forks

6Releases

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.

Major 0Minor 1Patch 5

Each point covers 5 days.

OpenSSF Scorecard 3.6 / 10

3.6aggregate

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-18 14:31 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0	CI-Tests	0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
10	Contributors	project has 4 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
2	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 2
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	47 existing vulnerabilities detected

Direct dependencies 4

Registry	Package	Version constraint	Manifest
npm	jsonpath-plus	`^10.1.0`	package.json
npm	just-clone	`^6.1.1`	package.json
npm	redis	`^4.6.4`	package.json
npm	ulid	`^2.3.0`	package.json

All dependencies 218

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

Registry	Package	Version	Relation
npm	jsonpath-plus	`10.1.0`	direct
npm	just-clone	`6.2.0`	direct
npm	redis	`4.6.4`	direct
npm	ulid	`2.3.0`	direct
npm	@bcoe/v8-coverage	`0.2.3`	indirect
npm	@esbuild/android-arm	`0.15.18`	indirect
npm	@esbuild/linux-loong64	`0.15.18`	indirect
npm	@istanbuljs/schema	`0.1.3`	indirect
npm	@jridgewell/resolve-uri	`3.1.0`	indirect
npm	@jridgewell/sourcemap-codec	`1.4.14`	indirect
npm	@jridgewell/trace-mapping	`0.3.17`	indirect
npm	@jsep-plugin/assignment	`1.2.1`	indirect
npm	@jsep-plugin/regex	`1.0.3`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@polka/url	`1.0.0-next.21`	indirect
npm	@redis/bloom	`1.2.0`	indirect
npm	@redis/client	`1.5.5`	indirect
npm	@redis/graph	`1.1.0`	indirect
npm	@redis/json	`1.0.4`	indirect
npm	@redis/search	`1.1.1`	indirect
npm	@redis/time-series	`1.0.4`	indirect
npm	@types/chai	`4.3.4`	indirect
npm	@types/chai-subset	`1.3.3`	indirect
npm	@types/istanbul-lib-coverage	`2.0.4`	indirect
npm	@types/node	`18.11.18`	indirect
npm	@vitest/ui	`0.17.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	any-promise	`1.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	array-union	`2.1.0`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	binary-extensions	`2.2.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	braces	`3.0.3`	indirect
npm	bundle-require	`3.1.2`	indirect
npm	c8	`7.12.0`	indirect
npm	cac	`6.7.14`	indirect
npm	chai	`4.3.7`	indirect
npm	check-error	`1.0.2`	indirect
npm	chokidar	`3.5.3`	indirect
npm	cliui	`7.0.4`	indirect
npm	cluster-key-slot	`1.1.2`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	commander	`4.1.1`	indirect
npm	concat-map	`0.0.1`	indirect
npm	convert-source-map	`1.9.0`	indirect
npm	cross-spawn	`7.0.3`	indirect
npm	debug	`4.3.4`	indirect
npm	deep-eql	`4.1.3`	indirect
npm	dir-glob	`3.0.1`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	esbuild	`0.15.18`	indirect
npm	esbuild-android-64	`0.15.18`	indirect
npm	esbuild-android-arm64	`0.15.18`	indirect
npm	esbuild-darwin-64	`0.15.18`	indirect
npm	esbuild-darwin-arm64	`0.15.18`	indirect
npm	esbuild-freebsd-64	`0.15.18`	indirect
npm	esbuild-freebsd-arm64	`0.15.18`	indirect
npm	esbuild-linux-32	`0.15.18`	indirect
npm	esbuild-linux-64	`0.15.18`	indirect
npm	esbuild-linux-arm	`0.15.18`	indirect
npm	esbuild-linux-arm64	`0.15.18`	indirect
npm	esbuild-linux-mips64le	`0.15.18`	indirect
npm	esbuild-linux-ppc64le	`0.15.18`	indirect
npm	esbuild-linux-riscv64	`0.15.18`	indirect
npm	esbuild-linux-s390x	`0.15.18`	indirect
npm	esbuild-netbsd-64	`0.15.18`	indirect
npm	esbuild-openbsd-64	`0.15.18`	indirect
npm	esbuild-sunos-64	`0.15.18`	indirect
npm	esbuild-windows-32	`0.15.18`	indirect
npm	esbuild-windows-64	`0.15.18`	indirect
npm	esbuild-windows-arm64	`0.15.18`	indirect
npm	escalade	`3.1.1`	indirect
npm	execa	`5.1.1`	indirect
npm	fast-glob	`3.2.12`	indirect
npm	fastq	`1.15.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	foreground-child	`2.0.0`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.2`	indirect
npm	function-bind	`1.1.1`	indirect
npm	generic-pool	`3.9.0`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-func-name	`2.0.2`	indirect
npm	get-stream	`6.0.1`	indirect
npm	glob	`7.1.6`	indirect
npm	glob	`7.2.3`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	globby	`11.1.0`	indirect
npm	handlebars	`4.7.7`	indirect
npm	has	`1.0.3`	indirect
npm	has-flag	`4.0.0`	indirect
npm	html-escaper	`2.0.2`	indirect
npm	human-signals	`2.1.0`	indirect
npm	ignore	`5.2.4`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-core-module	`2.11.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-stream	`2.0.1`	indirect
npm	isexe	`2.0.0`	indirect
npm	istanbul-lib-coverage	`3.2.0`	indirect
npm	istanbul-lib-report	`3.0.0`	indirect
npm	istanbul-reports	`3.1.5`	indirect
npm	joycon	`3.1.1`	indirect
npm	jsep	`1.3.9`	indirect
npm	jsonc-parser	`3.2.0`	indirect
npm	lilconfig	`2.0.6`	indirect
npm	lines-and-columns	`1.2.4`	indirect
npm	load-tsconfig	`0.2.3`	indirect
npm	local-pkg	`0.4.3`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.sortby	`4.7.0`	indirect
npm	loupe	`2.3.6`	indirect
npm	lunr	`2.3.9`	indirect
npm	make-dir	`3.1.0`	indirect
npm	marked	`4.2.12`	indirect
npm	merge-stream	`2.0.0`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.8`	indirect
npm	mimic-fn	`2.1.0`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimatch	`5.1.6`	indirect
npm	minimist	`1.2.7`	indirect
npm	mrmime	`1.0.1`	indirect
npm	ms	`2.1.2`	indirect
npm	mz	`2.7.0`	indirect
npm	nanoid	`3.3.7`	indirect
npm	neo-async	`2.6.2`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	npm-run-path	`4.0.1`	indirect
npm	object-assign	`4.1.1`	indirect
npm	once	`1.4.0`	indirect
npm	onetime	`5.1.2`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-type	`4.0.0`	indirect
npm	pathval	`1.1.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	pirates	`4.0.5`	indirect
npm	postcss	`8.4.47`	indirect
npm	postcss-load-config	`3.1.4`	indirect
npm	punycode	`2.3.0`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	resolve	`1.22.1`	indirect
npm	resolve-from	`5.0.0`	indirect
npm	reusify	`1.0.4`	indirect
npm	rimraf	`3.0.2`	indirect
npm	rollup	`2.79.2`	indirect
npm	rollup	`3.29.5`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	semver	`6.3.1`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	shiki	`0.12.1`	indirect
npm	signal-exit	`3.0.7`	indirect
npm	sirv	`2.0.2`	indirect
npm	slash	`3.0.0`	indirect
npm	source-map	`0.6.1`	indirect
npm	source-map	`0.8.0-beta.0`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-final-newline	`2.0.0`	indirect
npm	sucrase	`3.29.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	test-exclude	`6.0.0`	indirect
npm	thenify	`3.3.1`	indirect
npm	thenify-all	`1.6.0`	indirect
npm	tinypool	`0.2.4`	indirect
npm	tinyspy	`1.0.2`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	totalist	`3.0.0`	indirect
npm	tr46	`1.0.1`	indirect
npm	tree-kill	`1.2.2`	indirect
npm	ts-interface-checker	`0.1.13`	indirect
npm	tsup	`6.5.0`	indirect
npm	type-detect	`4.0.8`	indirect
npm	typedoc	`0.23.24`	indirect
npm	typedoc-plugin-markdown	`3.14.0`	indirect
npm	typescript	`4.9.5`	indirect
npm	uglify-js	`3.17.4`	indirect
npm	v8-to-istanbul	`9.0.1`	indirect
npm	vite	`3.2.11`	indirect
npm	vitest	`0.20.3`	indirect
npm	vscode-oniguruma	`1.7.0`	indirect
npm	vscode-textmate	`8.0.0`	indirect
npm	webidl-conversions	`4.0.2`	indirect
npm	whatwg-url	`7.1.0`	indirect
npm	which	`2.0.2`	indirect
npm	wordwrap	`1.0.0`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yallist	`4.0.0`	indirect
npm	yaml	`1.10.2`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.9`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:redis-om@0.4.7 pulls in 16 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records