Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 05:15 UTC

microsoft / PowerBI-JavaScript

JavaScript library for embedding Power BI into your apps. Check out the docs website and wiki for more information.

TypeScriptCustom license★ 1,137 stars⑂ 477 forkssince Sep 2015View on GitHub ↗

microsoft/PowerBI-JavaScript holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Community & Adoption (86/100) and lowest on Vitality (33/100). It was last updated 117 days ago. A single contributor accounts for most of its recent work.

67
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.

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

Ownership

MicrosoftOrganization
125,508 followers8,208 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmpowerbi-client2.24.11,432,1501034 days agomicrosoftpowerbiembeddedvisuals

Metrics by category

Vitality

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

33At Risk · 21% of overall
How it's scored
9.9/36Push recencylast push 117 days ago
5.5/36Commit cadence8/52 weeks with commits
10.8/18Commit volume15 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year15
human_commit_share
days_since_last_push117
active_weeks_last_year8
How it's scored
27/27Ships releases8 releases published
0/36Release recencylatest release 1,610 days ago
12.6/27Release cadencea release every ~285.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv2.19.1
releases_from_tagsno
days_since_latest_release1,610
mean_days_between_releases285.7
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?

86Excellent · 17% of overall
How it's scored
49.6/60Stars1,137 stars
22.3/25Forks477 forks
12.1/15Watchers149 watchers
Inputs used
forks477
stars1,137
watchers149
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,432,150 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespowerbi-client
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,432,150
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?

79Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
11/22.5Commit distributiontop contributor authored 51% of commits
13.5/13.5Contributor breadth39 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled39
top_contributor_share0.509
How it's scored
0/42Issue resolutionno issues or no data
22.6/30PR acceptance123/163 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs123
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs40
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach125,508 followers of microsoft
25/25Track record8,208 public repos, account ~12 yr old
Inputs used
followers125,508
owner_typeOrganization
is_verified
owner_loginmicrosoft
public_repos8,208
account_age_days4,605
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 4 days ago
20/20Version history103 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespowerbi-client
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 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
6/20OpenSSF Scorecard: CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

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?

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.8/2.5CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
4/5SASTSAST tool is not run on all commits -- score normalized to 8
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): 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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages5
unassessed_packages45
affected_by_severitynone
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 5 resolved dependencies against OSV. 45 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
53.7/55Manageable file sizes1/43 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes95,804
source_files_sampled43
oversized_source_files1

Key facts

1,137GitHub stars
39contributors
15commits, last 12 months
117days since last push
8releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • deps.dev does not index npm:powerbi-client@2.24.1; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 1,137 ★ / 0 ⇿
1,137Stars

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

02004006008001,0001,2001,13792017-072022-012026-07

Each point covers 9 days.

OpenSSF Scorecard 5.9 / 10
5.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-07-21 05:14 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
3CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
8SASTSAST tool is not run on all commits -- score normalized to 8
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmhttp-post-message^0.3.0package.json
npmpowerbi-models^2.0.1package.json
npmpowerbi-router^0.1package.json
npmwindow-post-message-proxy^0.3.0package.json
All dependencies 50

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

RegistryPackageVersionRelation
npmhttp-post-message^0.3.0direct
npmpowerbi-models^2.0.1direct
npmpowerbi-router^0.1direct
npmwindow-post-message-proxy^0.3.0direct
npm@types/jasmine^3.5.10indirect
npm@types/jquery^3.3.34indirect
npm@types/jsen0.0.19indirect
npm@types/karma-jasmine^3.1.0indirect
npm@types/node^14.14.7indirect
npm@types/npm^2.0.31indirect
npm@typescript-eslint/eslint-plugin^4.7.0indirect
npm@typescript-eslint/parser^4.7.0indirect
npmdel^2.2.2indirect
npmes6-promise^3.2.1indirect
npmeslint^7.13.0indirect
npmeslint-plugin-import^2.22.1indirect
npmeslint-plugin-jsdoc^30.7.7indirect
npmeslint-plugin-prefer-arrow^1.2.2indirect
npmgulp^4.0.2indirect
npmgulp-eslint^6.0.0indirect
npmgulp-flatten^0.4.0indirect
npmgulp-help-four^0.2.3indirect
npmgulp-prepend^0.3.0indirect
npmgulp-rename^1.2.2indirect
npmgulp-replace^0.5.4indirect
npmgulp-typedoc^2.0.0indirect
npmgulp-typescript^6.0.0-alpha.1indirect
npmgulp-watch^5.0.1indirect
npmgulp4-run-sequence^1.0.0indirect
npmhttp-server^14.1.1indirect
npmignore-loader^0.1.1indirect
npmjasmine-core3.10.1indirect
npmjquery^3.3.1indirect
npmjson-loader^0.5.4indirect
npmkarma^6.4.4indirect
npmkarma-chrome-launcher^3.1.0indirect
npmkarma-coverage~2.0.3indirect
npmkarma-firefox-launcher^1.2.0indirect
npmkarma-jasmine4.0.1indirect
npmkarma-jasmine-html-reporter1.7.0indirect
npmkarma-junit-reporter^2.0.1indirect
npmkarma-spec-reporter0.0.32indirect
npmkarma-typescript^5.5.4indirect
npmpuppeteer^24.26.0indirect
npmts-loader^6.2.2indirect
npmtypedoc^0.23.23indirect
npmtypescript~4.6.0indirect
npmwebpack^5.75.0indirect
npmwebpack-stream^7.0.0indirect
npmyargs^16.1.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 5 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 45 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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

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