Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 20:28 UTC

adobe / aio-lib-telemetry

A utility module for easy instrumentation of Adobe App Builder runtime actions via OpenTelemetry.

TypeScriptApache-2.0★ 3 stars⑂ 2 forkssince Jul 2025View on GitHub ↗

adobe/aio-lib-telemetry holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (83/100) and lowest on Community & Adoption (51/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

81
overall / 100
Excellent

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.

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

Ownership

Adobe, Inc.Organization · verified domain
3,438 followers1,129 public repossince Nov 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@adobe/aio-lib-telemetry1.3.02,5009105 days agoaioadobe-ioaio-telemetryaio-opentelemetry

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
11.8/36Commit cadence — 17/52 weeks with commits
16.7/18Commit volume — 72 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year72
human_commit_share0.29
days_since_last_push1
active_weeks_last_year17
How it's scored
27/27Ships releases — 9 releases published
27/36Release recency — latest release 105 days ago
19.8/27Release cadence — a release every ~46.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count9
latest_release_tagv1.3.0
releases_from_tagsno
days_since_latest_release105
mean_days_between_releases46.4
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?

51Moderate · 17% of overall
How it's scored
4.9/60Stars — 3 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars3
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
45.3/80Monthly downloads — 2,500 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@adobe/aio-lib-telemetry
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,500
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.4/22.5Commit distribution — top contributor authored 94% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.938
How it's scored
21/42Issue resolution — 50% of issues closed
25.1/30PR acceptance — 118/141 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 5/8 approved changesets -- score normalized to 6
Inputs used
merged_prs118
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs23
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
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 3,438 followers of adobe
25/25Track record — 1,129 public repos, account ~16 yr old
Inputs used
followers3,438
owner_typeOrganization
is_verifiedyes
owner_loginadobe
public_repos1,129
account_age_days5,852

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 105 days ago
20/20Version history — 9 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@adobe/aio-lib-telemetry
ecosystemsnpm
any_deprecatedno
min_days_since_publish105

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicsadobe, adobe-io, app-builder, open-telemetry, adobe-app-builder, adobe-open-telemetry, aio-telemetry
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 5/8 approved changesets -- score normalized to 6
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
18.8/35Direct dependencies free of known advisories — 1 affected: @opentelemetry/instrumentation-http 0.221.0 (moderate 5.8)
12.7/25Indirect dependencies free of known advisories — 2 affected: glob 10.5.0 (moderate 5.3), minimatch 9.0.9 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories3
affected_packages3
assessed_packages221
unassessed_packages0
affected_by_severitymoderate 3
direct_affected_packages1
Matched the npm:@adobe/aio-lib-telemetry@1.3.0 runtime dependency closure — what installing the published package pulls in — 221 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.

83Excellent · 4% of overall
How it's scored
45/45Agent instructions — .claude/CLAUDE.md, .cursor/rules/ultracite.mdc, .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 27 of 29 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.931
agent_instruction_files.claude/CLAUDE.md, .cursor/rules/ultracite.mdc, .github/copilot-instructions.md
agent_instruction_max_bytes20,455
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — .github/scripts/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 64 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs.github/scripts/tsconfig.json, tsconfig.json
agent_commit_share0.04
toolchain_manifests—
dependency_bot_commit_share0.64
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/46 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes27,502
source_files_sampled46
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

3GitHub stars
3contributors
72commits, last 12 months
1days since last push
9releases
1bus factor
1open 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 ★ / 2 ⇿
0Stars
2Forks
7Releases

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.

111222212025-082026-012026-07
Major 1Minor 2Patch 4
OpenSSF Scorecard 6.9 / 10
6.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-11-18 20:28 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 5/8 approved changesets -- score normalized to 6
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 28
RegistryPackageVersion constraintManifest
npm@adobe/aio-lib-core-logging^3.0.2package.json
npm@opentelemetry/api^1.9.1package.json
npm@opentelemetry/api-logs^0.222.0package.json
npm@opentelemetry/auto-instrumentations-node^0.80.0package.json
npm@opentelemetry/exporter-logs-otlp-grpc^0.222.0package.json
npm@opentelemetry/exporter-logs-otlp-http^0.222.0package.json
npm@opentelemetry/exporter-logs-otlp-proto^0.222.0package.json
npm@opentelemetry/exporter-metrics-otlp-grpc^0.222.0package.json
npm@opentelemetry/exporter-metrics-otlp-http^0.222.0package.json
npm@opentelemetry/exporter-metrics-otlp-proto^0.222.0package.json
npm@opentelemetry/exporter-trace-otlp-grpc^0.222.0package.json
npm@opentelemetry/exporter-trace-otlp-http^0.222.0package.json
npm@opentelemetry/exporter-trace-otlp-proto^0.222.0package.json
npm@opentelemetry/instrumentation^0.222.0package.json
npm@opentelemetry/instrumentation-graphql^0.70.0package.json
npm@opentelemetry/instrumentation-http^0.222.0package.json
npm@opentelemetry/instrumentation-undici^0.32.0package.json
npm@opentelemetry/otlp-exporter-base^0.222.0package.json
npm@opentelemetry/otlp-grpc-exporter-base^0.222.0package.json
npm@opentelemetry/resources^2.7.1package.json
npm@opentelemetry/sdk-logs^0.222.0package.json
npm@opentelemetry/sdk-metrics^2.7.1package.json
npm@opentelemetry/sdk-node^0.222.0package.json
npm@opentelemetry/sdk-trace-node^2.7.1package.json
npm@opentelemetry/semantic-conventions^1.41.1package.json
npm@opentelemetry/winston-transport^0.32.0package.json
npmdeepmerge^4.3.1package.json
npmwinston-transport^4.9.0package.json
All dependencies 15

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

RegistryPackageVersionRelation
npm@pnpm/exe.android-arm6412.4.1indirect
npm@pnpm/exe.android-x6412.4.1indirect
npm@pnpm/exe.darwin-arm6412.4.1indirect
npm@pnpm/exe.darwin-x6412.4.1indirect
npm@pnpm/exe.freebsd-x6412.4.1indirect
npm@pnpm/exe.linux-arm6412.4.1indirect
npm@pnpm/exe.linux-arm64-musl12.4.1indirect
npm@pnpm/exe.linux-ppc6412.4.1indirect
npm@pnpm/exe.linux-riscv6412.4.1indirect
npm@pnpm/exe.linux-s390x12.4.1indirect
npm@pnpm/exe.linux-x6412.4.1indirect
npm@pnpm/exe.linux-x64-musl12.4.1indirect
npm@pnpm/exe.win32-arm6412.4.1indirect
npm@pnpm/exe.win32-x6412.4.1indirect
npmpnpm12.4.1indirect
Dependency advisories 3

Installing npm:@adobe/aio-lib-telemetry@1.3.0 pulls in 221 packages, direct and transitive: 3 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
@opentelemetry/instrumentation-http0.221.0directmoderate10.222.0
glob10.5.0indirectmoderate114.0.2
minimatch9.0.9indirectmoderate111.0.1

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

How one result sits in the wider record: aggregate statistics — npm.