Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 10:47 UTC

sensorsdata / sa-sdk-javascript

神策数据官方 Web JavaScript 埋点 SDK，是一款轻量级用于 Web 端和 H5 端的数据采集埋点 SDK。使用原生 JavaScript 技术实现代码埋点、全埋点、可视化全埋点、网页热力图和触达图等功能。

JavaScriptCustom license★ 957 stars⑂ 541 forkssince Nov 2015View on GitHub ↗

sensorsdata/sa-sdk-javascript holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (72/100) and lowest on AI Readiness (3/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

Sensors DataOrganization

291 followers96 public repossince Nov 2015

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	sa-sdk-javascript	1.27.14	1,852,682	247	34 days ago	sensorsdata javascript sdk

Metrics by category

Vitality

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

61Moderate · 21% of overall

Development activity

41Weak

How it's scored

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

Inputs used

commits_last_year	5
human_commit_share	1
days_since_last_push	8
active_weeks_last_year	5

Release discipline

92Excellent

How it's scored

27/27	Ships releases — 100 releases published
36/36	Release recency — latest release 8 days ago
19.8/27	Release cadence — a release every ~47.5 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	100
latest_release_tag	v1.28.1
releases_from_tags	no
days_since_latest_release	8
mean_days_between_releases	47.5

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?

72Good · 17% of overall

Popularity & adoption

80Excellent

How it's scored

48.3/60	Stars — 957 stars
22.8/25	Forks — 541 forks
8.5/15	Watchers — 35 watchers

Inputs used

forks	541
stars	957
watchers	35
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

44Weak

How it's scored

22.5/22.5	README
16.9/22.5	License — license file present, not a recognized license
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	2
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 1,852,682 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	sa-sdk-javascript
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	1,852,682
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?

61Moderate · 23% of overall

Maintainer resilience (bus factor)

23At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
6.1/22.5	Commit distribution — top contributor authored 73% of commits
8.1/13.5	Contributor breadth — 6 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	1
contributors_sampled	6
top_contributor_share	0.73

Issue & PR responsiveness

65Good

How it's scored

41.2/42	Issue resolution — 98% of issues closed
15/30	PR acceptance — 4/8 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	4
open_issues	2
closed_issues	100
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.98
closed_unmerged_prs	4
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

73Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
17.7/25	Owner reach — 291 followers of sensorsdata
25/25	Track record — 96 public repos, account ~10 yr old

Inputs used

followers	291
owner_type	Organization
is_verified	no
owner_login	sensorsdata
public_repos	96
account_age_days	3,969

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	sa-sdk-javascript
ecosystems	npm
any_deprecated	no
min_days_since_publish	34

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall

Engineering practices

1Critical

How it's scored

0/24	CI workflows
0/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	no
has_tests	no
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 — http://opensource.sensorsdata.cn
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	http://opensource.sensorsdata.cn
docs_site	http://opensource.sensorsdata.cn
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?

39Weak · 16% of overall

Security posture

39Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
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
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10	Dangerous-Workflow — no data
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.2/2.5	License — license file detected
1.5/7.5	Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	3.9

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

3Critical · 4% of overall

Agent context & guidance

1Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

1Critical

How it's scored

0/18	One-command bootstrap
0/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
0/10	Reproducible environment
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
lockfiles	—
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

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

Code legibility for models

14Critical

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
13.8/55	Manageable file sizes — 9/12 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	206,688
source_files_sampled	12
oversized_source_files	9

Key facts

957GitHub stars

6contributors

5commits, last 12 months

8days since last push

100releases

1bus factor

2open 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 ★ / 541 ⇿

0Stars

541Forks

99Releases

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 0Patch 99

Each point covers 10 days.

OpenSSF Scorecard 3.9 / 10

3.9aggregate

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 10:47 UTC

10	Binary-Artifacts	no binaries found in the repo
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
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
n/a	Dangerous-Workflow	no workflows found
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
9	License	license file detected
2	Maintained	3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
10	Vulnerabilities	0 existing vulnerabilities detected

All dependencies 0

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

Registry	Package	Version	Relation

Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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