Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 03:20 UTC

tomas / needle

Nimble, streamable HTTP client for Node.js. With proxy, iconv, cookie, deflate & multipart support.

JavaScript · HTMLMIT★ 1,634 stars⑂ 237 forkssince Dec 2011View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

tomas/needle holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (74/100) and lowest on Security (42/100). It was last updated 43 days ago. A single contributor accounts for most of its recent work.

57
overall / 100
Moderate

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.

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

Ownership

Tomás PollakPersonal account
495 followers103 public repossince May 2008Bolder, Ltd

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmneedle3.5.055,194,785115153 days agohttphttpssimplerequestclientmultipartuploadproxydeflatetimeoutcharseticonvcookieredirect

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
18/36Push recencylast push 43 days ago
2.8/36Commit cadence4/52 weeks with commits
11.5/18Commit volume18 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year18
human_commit_share1
days_since_last_push43
active_weeks_last_year4
How it's scored
27/27Ships releases35 releases published
0/36Release recencylatest release 1,365 days ago
27/27Release cadencea release every ~24.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count35
latest_release_tagv3.2.0
releases_from_tagsno
days_since_latest_release1,365
mean_days_between_releases24.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?

74Good · 17% of overall
How it's scored
52.1/60Stars1,634 stars
19.8/25Forks237 forks
8/15Watchers28 watchers
Inputs used
forks237
stars1,634
watchers28
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads55,194,785 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesneedle
dependents
ecosystemsnpm
total_downloads
monthly_downloads55,194,785
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth72 contributors
10/10OpenSSF Scorecard: Contributorsproject has 21 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled72
top_contributor_share0.798
How it's scored
30.2/42Issue resolution72% of issues closed
20.4/30PR acceptance104/153 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 9/19 approved changesets -- score normalized to 4
Inputs used
merged_prs104
open_issues81
closed_issues208
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.72
closed_unmerged_prs49
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
19.4/25Owner reach495 followers of tomas
25/25Track record103 public repos, account ~18 yr old
Inputs used
followers495
owner_typeUser
is_verified
owner_logintomas
public_repos103
account_age_days6,662
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 153 days ago
20/20Version history115 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesneedle
ecosystemsnpm
any_deprecatedno
min_days_since_publish153

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.npmjs.com/package/needle
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://www.npmjs.com/package/needle
docs_sitehttps://www.npmjs.com/package/needle
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 9/19 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 21 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities14 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:needle@3.5.0 runtime dependency closure — what installing the published package pulls in — 3 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
23.5/40Legible commit history44 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.44
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/51 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes34,129
source_files_sampled51
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

1,634GitHub stars
72contributors
18commits, last 12 months
43days since last push
35releases
1bus factor
81open 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 ★ / 237 ⇿
0Stars
237Forks
35Releases

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.

0408012016020024022852012-032019-032026-02
Major 2Minor 21Patch 12

Each point covers 13 days.

OpenSSF Scorecard 2.8 / 10
2.8aggregate

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-08-13 03:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 9/19 approved changesets -- score normalized to 4
10Contributorsproject has 21 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities14 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmiconv-lite^0.6.3package.json
npmsax^1.2.4package.json
All dependencies 56

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

RegistryPackageVersionRelation
npmiconv-lite0.6.3direct
npmsax1.2.4direct
npmbalanced-match1.0.2indirect
npmbody-parser^1.20.1indirect
npmbrace-expansion1.1.11indirect
npmbrowser-stdout1.3.1indirect
npmcommander2.15.1indirect
npmconcat-map0.0.1indirect
npmdebug3.1.0indirect
npmdiff3.5.0indirect
npmend-of-stream1.4.4indirect
npmescape-string-regexp1.0.5indirect
npmexpress^4.18.2indirect
npmformatio1.2.0indirect
npmfs-extra^10.1.0indirect
npmfs.realpath1.0.0indirect
npmglob7.1.2indirect
npmgrowl1.10.5indirect
npmhas-flag3.0.0indirect
npmhe1.1.1indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmisarray0.0.1indirect
npmjschardet1.6.0indirect
npmjsonparse1.3.1indirect
npmJSONStream1.3.5indirect
npmlolex1.6.0indirect
npmminimatch3.0.4indirect
npmminimist0.0.8indirect
npmmkdirp0.5.1indirect
npmmocha5.2.0indirect
npmms2.0.0indirect
npmms2.1.1indirect
npmnative-promise-only0.8.1indirect
npmneedle^3.1.0indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-to-regexp1.8.0indirect
npmpump3.0.0indirect
npmq1.5.1indirect
npmsafer-buffer2.1.2indirect
npmsamsam1.3.0indirect
npmshould13.2.3indirect
npmshould-equal2.0.0indirect
npmshould-format3.0.3indirect
npmshould-type1.4.0indirect
npmshould-type-adaptors1.1.0indirect
npmshould-util1.0.0indirect
npmsinon2.3.0indirect
npmsupports-color5.4.0indirect
npmtext-encoding0.6.4indirect
npmthrough2.3.8indirect
npmtype-detect4.0.8indirect
npmwrappy1.0.2indirect
npmxml2js0.4.19indirect
npmxmlbuilder9.0.7indirect
Dependency advisories 0

Installing npm:needle@3.5.0 pulls in 3 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.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.