Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 08:08 UTC

equinor / isar

Integration and Supervisory control of Autonomous Robots

PythonEPL-2.0★ 19 stars⑂ 45 forkssince Sep 2021View on GitHub ↗
KindCommand-line toolLibraryNetwork servicehow this is determined

equinor/isar holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (99/100) and lowest on AI Readiness (44/100). It was last updated today. 3 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

EquinorOrganization · verified domain
1,846 followers762 public repossince Dec 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIisar2.7.03,5362040 days ago

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 372 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year372
human_commit_share0.97
days_since_last_push0
active_weeks_last_year49

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~4.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.7.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases4.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?

48Weak · 17% of overall
How it's scored
20.4/60Stars — 19 stars
13.7/25Forks — 45 forks
0/15Watchers — 2 watchers
Inputs used
forks45
stars19
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (EPL-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/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_templateyes
How it's scored
47.3/80Monthly downloads — 3,536 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesisar
dependents—
ecosystemspypi
total_downloads—
monthly_downloads3,536
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?

89Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.7/22.5Commit distribution — top contributor authored 26% of commits
13.5/13.5Contributor breadth — 32 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor3
contributors_sampled32
top_contributor_share0.256
How it's scored
41.5/42Issue resolution — 99% of issues closed
25.6/30PR acceptance — 720/843 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 14/17 approved changesets -- score normalized to 8
Inputs used
merged_prs720
open_issues5
closed_issues373
prs_merged_7d4
prs_decided_7d5
prs_merged_30d15
prs_decided_30d17
issue_closed_ratio0.987
closed_unmerged_prs123
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
23.5/25Owner reach — 1,846 followers of equinor
25/25Track record — 762 public repos, account ~15 yr old
Inputs used
followers1,846
owner_typeOrganization
is_verifiedyes
owner_loginequinor
public_repos762
account_age_days5,787

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 204 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesisar
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black], [tool.isort])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 20 out of 20 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicshacktoberfest
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?

79Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 20 out of 20 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
6/7.5Code-Review — Found 14/17 approved changesets -- score normalized to 8
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.4
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 advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages96
unassessed_packages0
affected_by_severityhigh 1, moderate 1
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 96 resolved dependencies against OSV. 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.1/40Legible commit history — 2 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.021
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.black], [tool.isort])
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/172 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes16,872
source_files_sampled172
oversized_source_files0

Key facts

19GitHub stars
32contributors
372commits, last 12 months
0days since last push
100releases
3bus factor
5open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:isar@2.7.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 45 ⇿
0Stars
45Forks
83Releases

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.

01325385045102021-102024-032026-08
Major 1Minor 12Patch 70

Each point covers 5 days.

OpenSSF Scorecard 7.4 / 10
7.4aggregate

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-10-21 08:07 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 14/17 approved changesets -- score normalized to 8
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 28
RegistryPackageVersion constraintManifest
PyPIalitra>=1.1.3pyproject.toml
PyPIazure-identity—pyproject.toml
PyPIazure-storage-blob—pyproject.toml
PyPIbackoff—pyproject.toml
PyPIclick—pyproject.toml
PyPIdacite—pyproject.toml
PyPIfastapi-azure-auth—pyproject.toml
PyPIfastapi>=0.121.0pyproject.toml
PyPIdependency-injector—pyproject.toml
PyPInumpy—pyproject.toml
PyPIpaho-mqtt—pyproject.toml
PyPIpydantic_settings—pyproject.toml
PyPIpydantic—pyproject.toml
PyPIPyJWT—pyproject.toml
PyPIpython-dotenv—pyproject.toml
PyPIPyYAML—pyproject.toml
PyPIrequests-toolbelt—pyproject.toml
PyPIrequests—pyproject.toml
PyPIstarlette>=0.49.1pyproject.toml
PyPItransitions—pyproject.toml
PyPIuvicorn—pyproject.toml
PyPIopentelemetry-api==1.38.0pyproject.toml
PyPIopentelemetry-sdk—pyproject.toml
PyPIopentelemetry-exporter-otlp—pyproject.toml
PyPIopentelemetry-instrumentation-fastapi—pyproject.toml
PyPIpymysql—pyproject.toml
PyPIsqlalchemy—pyproject.toml
PyPIpsycopg>=3.3.6pyproject.toml
All dependencies 96

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

RegistryPackageVersionRelation
PyPIalitra2.0.0direct
PyPIazure-identity1.25.3direct
PyPIazure-storage-blob12.30.1direct
PyPIbackoff2.2.1direct
PyPIclick8.5.0direct
PyPIdacite1.9.2direct
PyPIdependency-injector4.49.1direct
PyPIfastapi0.141.1direct
PyPIfastapi-azure-auth5.3.0direct
PyPInumpy2.5.2direct
PyPIopentelemetry-api1.38.0direct
PyPIopentelemetry-exporter-otlp1.38.0direct
PyPIopentelemetry-instrumentation-fastapi0.59b0direct
PyPIopentelemetry-sdk1.38.0direct
PyPIpaho-mqtt2.1.0direct
PyPIpsycopg3.3.6direct
PyPIpydantic2.13.5direct
PyPIpydantic-settings2.15.0direct
PyPIpyjwt2.15.0direct
PyPIpymysql1.2.0direct
PyPIpython-dotenv1.2.3direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPIrequests-toolbelt1.0.0direct
PyPIsqlalchemy2.0.52direct
PyPIstarlette1.6.0direct
PyPItransitions0.9.3direct
PyPIuvicorn0.52.4direct
PyPIalembic1.19.1indirect
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.0indirect
PyPIasgiref3.12.1indirect
PyPIast-serialize0.9.0indirect
PyPIazure-core1.41.0indirect
PyPIblack26.5.1indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.5.1indirect
PyPIcolorama0.4.6indirect
PyPIcryptography50.0.1indirect
PyPIdocker7.2.0indirect
PyPIexecnet2.1.2indirect
PyPIgoogleapis-common-protos1.75.3indirect
PyPIgreenlet3.5.5indirect
PyPIgrpcio1.83.1indirect
PyPIh110.16.0indirect
PyPIhttpcore22.12.0indirect
PyPIhttpx22.12.0indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidna3.19indirect
PyPIimportlib-metadata8.7.1indirect
PyPIiniconfig2.3.0indirect
PyPIisodate0.7.2indirect
PyPIisort9.0.1indirect
PyPIlibrt0.15.0indirect
PyPImako1.4.1indirect
PyPImarkupsafe3.0.3indirect
PyPImsal1.38.0indirect
PyPImsal-extensions1.3.1indirect
PyPImypy2.3.1indirect
PyPImypy-extensions1.1.0indirect
PyPIopentelemetry-exporter-otlp-proto-common1.38.0indirect
PyPIopentelemetry-exporter-otlp-proto-grpc1.38.0indirect
PyPIopentelemetry-exporter-otlp-proto-http1.38.0indirect
PyPIopentelemetry-instrumentation0.59b0indirect
PyPIopentelemetry-instrumentation-asgi0.59b0indirect
PyPIopentelemetry-proto1.38.0indirect
PyPIopentelemetry-semantic-conventions0.59b0indirect
PyPIopentelemetry-util-http0.59b0indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.7indirect
PyPIpluggy1.6.0indirect
PyPIprotobuf6.33.6indirect
PyPIpsycopg-binary3.3.6indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.5indirect
PyPIpygments2.21.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-mock3.15.1indirect
PyPIpytest-xdist3.8.0indirect
PyPIpytokens0.4.1indirect
PyPIpywin32312indirect
PyPIrequests-mock1.12.1indirect
PyPIruff0.16.6indirect
PyPIscipy1.18.1indirect
PyPIsix1.17.0indirect
PyPItestcontainers4.15.0indirect
PyPItruststore0.10.4indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPItzdata2026.5indirect
PyPIurllib32.8.0indirect
PyPIwrapt1.17.3indirect
PyPIzipp4.1.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 96 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2026.7.22indirecthigh22026.10.19
mako1.4.1indirectmoderate21.4.2

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 — PyPI.