Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 20:21 UTC

frida / frida-node

Frida Node.js bindings

Python · C · TypeScriptNo license detected★ 329 stars⑂ 79 forkssince Mar 2015View on GitHub ↗

frida/frida-node holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (55/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

overall / 100

Good

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

Ownership

FridaOrganization

1,766 followers167 public repossince Apr 2013

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	frida	17.18.0	125,294	756	5 days ago	debugger tracer instrumentation hooking inject windows macos linux ios iphone ipad android

Metrics by category

Vitality

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

90Excellent · 21% of overall

Development activity

91Excellent

How it's scored

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

Inputs used

commits_last_year	270
human_commit_share	1
days_since_last_push	5
active_weeks_last_year	39

Release discipline

88Excellent

How it's scored

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

Inputs used

releases_count	100
latest_release_tag	17.18.0
releases_from_tags	yes
days_since_latest_release	5
mean_days_between_releases	8.8

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?

55Moderate · 17% of overall

Popularity & adoption

62Moderate

How it's scored

40.8/60	Stars — 329 stars
15.8/25	Forks — 79 forks
5.3/15	Watchers — 10 watchers

Inputs used

forks	79
stars	329
watchers	10
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

25At Risk

How it's scored

22.5/22.5	README
0/22.5	License — no license file detected
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	no
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 — 125,294 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	frida
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	125,294
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?

65Good · 23% of overall

Maintainer resilience (bus factor)

33At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	10
top_contributor_share	0.964

Issue & PR responsiveness

61Moderate

How it's scored

28.2/42	Issue resolution — 67% of issues closed
25.1/30	PR acceptance — 36/43 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	36
open_issues	24
closed_issues	49
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.671
closed_unmerged_prs	7
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

78Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
23.3/25	Owner reach — 1,766 followers of frida
25/25	Track record — 167 public repos, account ~13 yr old

Inputs used

followers	1,766
owner_type	Organization
is_verified	no
owner_login	frida
public_repos	167
account_age_days	4,909

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	frida
ecosystems	npm
any_deprecated	no
min_days_since_publish	5

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall

Engineering practices

60Moderate

How it's scored

24/24	CI workflows — 1 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 — no data

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

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

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://frida.re
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	https://frida.re
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

57Moderate · 16% of overall

Security posture

46Weak

How it's scored

5.2/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 20 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
0/2.5	License — license file not detected
7.5/7.5	Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
1.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
7.5/7.5	Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5	Vulnerabilities — 16 existing vulnerabilities detected

Inputs used

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

Excluded from scoring (no data or not applicable): CI-Tests, 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	40
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:frida@17.18.0 runtime dependency closure — what installing the published package pulls in — 40 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.

65Good · 4% of overall

Agent context & guidance

40Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	1
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

64Moderate

How it's scored

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

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	no
bootstrap_files	Makefile
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

81Excellent

How it's scored

27/45	Type-checkable code — Python with type-check config (tsconfig.json)
54.2/55	Manageable file sizes — 1/70 source files over 60KB

Inputs used

primary_language	Python
largest_source_bytes	81,391
source_files_sampled	70
oversized_source_files	1

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
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

329GitHub stars

10contributors

270commits, last 12 months

5days since last push

100releases

1bus factor

24open 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 ★ / 79 ⇿

0Stars

79Forks

79Releases

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 1Minor 9Patch 69

Each point covers 11 days.

OpenSSF Scorecard 4.6 / 10

4.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-14 20:21 UTC

7	Binary-Artifacts	binaries present in source code
0	Branch-Protection	branch protection not enabled on development/release branches
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/30 approved changesets -- score normalized to 0
10	Contributors	project has 20 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
0	License	license file not detected
10	Maintained	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
3	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 3
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
10	Token-Permissions	GitHub workflow tokens follow principle of least privilege
0	Vulnerabilities	16 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	bindings	`^1.5.0`	package.json
npm	minimatch	`^10.0.1`	package.json
npm	prebuild-install	`^7.1.3`	package.json

All dependencies 159

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

Registry	Package	Version	Relation
npm	bindings	`1.5.0`	direct
npm	minimatch	`10.0.1`	direct
npm	minimatch	`5.1.6`	direct
npm	minimatch	`9.0.5`	direct
npm	prebuild-install	`7.1.3`	direct
npm	@cspotcode/source-map-support	`0.8.1`	indirect
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@jridgewell/resolve-uri	`3.1.1`	indirect
npm	@jridgewell/sourcemap-codec	`1.4.15`	indirect
npm	@jridgewell/trace-mapping	`0.3.9`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	@tsconfig/node10	`1.0.9`	indirect
npm	@tsconfig/node12	`1.0.11`	indirect
npm	@tsconfig/node14	`1.0.3`	indirect
npm	@tsconfig/node16	`1.0.4`	indirect
npm	@types/bindings	`1.5.5`	indirect
npm	@types/chai	`5.2.1`	indirect
npm	@types/deep-eql	`4.0.2`	indirect
npm	@types/mocha	`10.0.10`	indirect
npm	@types/node	`22.13.16`	indirect
npm	acorn	`8.10.0`	indirect
npm	acorn-walk	`8.2.0`	indirect
npm	ansi-colors	`4.1.3`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.1.0`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.1`	indirect
npm	anymatch	`3.1.3`	indirect
npm	arg	`4.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	assertion-error	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	base64-js	`1.5.1`	indirect
npm	binary-extensions	`2.2.0`	indirect
npm	bl	`4.1.0`	indirect
npm	brace-expansion	`2.0.2`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	buffer	`5.7.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chai	`5.2.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	check-error	`2.1.1`	indirect
npm	chokidar	`3.5.3`	indirect
npm	chownr	`1.1.4`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	create-require	`1.1.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.0`	indirect
npm	decamelize	`4.0.0`	indirect
npm	decompress-response	`6.0.0`	indirect
npm	deep-eql	`5.0.2`	indirect
npm	deep-extend	`0.6.0`	indirect
npm	detect-libc	`2.0.2`	indirect
npm	diff	`4.0.2`	indirect
npm	diff	`5.2.0`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	end-of-stream	`1.4.4`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	expand-template	`2.0.3`	indirect
npm	file-uri-to-path	`1.0.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	fs-constants	`1.0.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	github-from-package	`0.0.0`	indirect
npm	glob	`10.5.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	ieee754	`1.2.1`	indirect
npm	inherits	`2.0.4`	indirect
npm	ini	`1.3.8`	indirect
npm	is-binary-path	`2.1.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-plain-obj	`2.1.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	js-yaml	`4.1.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	loupe	`3.1.3`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	lru-cache	`6.0.0`	indirect
npm	make-error	`1.3.6`	indirect
npm	mimic-response	`3.1.0`	indirect
npm	minimist	`1.2.8`	indirect
npm	minipass	`7.1.2`	indirect
npm	mkdirp-classic	`0.5.3`	indirect
npm	mocha	`11.1.0`	indirect
npm	ms	`2.1.3`	indirect
npm	napi-build-utils	`2.0.0`	indirect
npm	node-abi	`3.51.0`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	pathval	`2.0.0`	indirect
npm	picomatch	`2.3.1`	indirect
npm	pump	`3.0.0`	indirect
npm	randombytes	`2.1.0`	indirect
npm	rc	`1.2.8`	indirect
npm	readable-stream	`3.6.2`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	semver	`7.5.4`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	simple-concat	`1.0.1`	indirect
npm	simple-get	`4.0.1`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	string_decoder	`1.3.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.1.0`	indirect
npm	strip-json-comments	`2.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	tar-fs	`2.1.4`	indirect
npm	tar-stream	`2.2.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	ts-node	`10.9.2`	indirect
npm	tunnel-agent	`0.6.0`	indirect
npm	typescript	`5.8.2`	indirect
npm	undici-types	`6.20.0`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	v8-compile-cache-lib	`3.0.1`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`6.5.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yallist	`4.0.0`	indirect
npm	yargs	`17.7.2`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yn	`3.1.1`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:frida@17.18.0 pulls in 40 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