Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 14:45 UTC

posit-dev / vip

extensible test suite for verifying installations of posit team

PythonMIT★ 8 stars⑂ 1 forksince Feb 2026View on GitHub ↗
KindCommand-line toolPluginNetwork servicehow this is determined

posit-dev/vip holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (88/100) and lowest on Community & Adoption (39/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

posit-devOrganization
1,015 followers219 public repossince Jun 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIposit-vip2026.8.24,9151381 day ago

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume505 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year505
human_commit_share0.86
days_since_last_push0
active_weeks_last_year28
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~2.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv2026.8.2
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases2.4

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

39Weak · 17% of overall
How it's scored
13.7/60Stars8 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars8
watchers1
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
49.2/80Monthly downloads4,915 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesposit-vip
dependents
ecosystemspypi
total_downloads
monthly_downloads4,915
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?

69Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.2/22.5Commit distributiontop contributor authored 59% of commits
13.5/13.5Contributor breadth12 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.591
How it's scored
37.5/42Issue resolution89% of issues closed
26.5/30PR acceptance353/399 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/24 approved changesets -- score normalized to 0
Inputs used
merged_prs353
open_issues22
closed_issues184
prs_merged_7d9
prs_decided_7d9
prs_merged_30d47
prs_decided_30d50
issue_closed_ratio0.893
closed_unmerged_prs46
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 backingorganization-owned
0/20Verified domain
21.6/25Owner reach1,015 followers of posit-dev
21.4/25Track record219 public repos, account ~4 yr old
Inputs used
followers1,015
owner_typeOrganization
is_verifiedno
owner_loginposit-dev
public_repos219
account_age_days1,534

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 1 days ago
20/20Version history138 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesposit-vip
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows21 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://posit-dev.github.io/vip/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://posit-dev.github.io/vip/
docs_sitehttps://posit-dev.github.io/vip/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/24 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities42 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4.9

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_packages69
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 pypi:posit-vip@2026.8.2 runtime dependency closure — what installing the published package pulls in — 69 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://quarto.org/llms.txt)
40/40Legible commit history86 of 86 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://quarto.org/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes38,276
How it's scored
18/18One-command bootstrapjustfile
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/vip/py.typed, website/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice23 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance10 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, uv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/vip/py.typed, website/tsconfig.json
agent_commit_share0.23
toolchain_manifests
dependency_bot_commit_share0.1
How it's scored
27/45Type-checkable codePython with type-check config (src/vip/py.typed, website/tsconfig.json)
53.5/55Manageable file sizes5/185 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes127,538
source_files_sampled185
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

8GitHub stars
12contributors
505commits, last 12 months
0days since last push
100releases
1bus factor
22open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.9 / 10
4.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-08-22 14:45 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/24 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities42 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
PyPIfilelock>=3.12,<4pyproject.toml
PyPIhttpx>=0.27,<1pyproject.toml
PyPIplaywright==1.62.0pyproject.toml
PyPIpyotp~=2.9pyproject.toml
PyPIpytest==9.1.1pyproject.toml
PyPIpytest-bdd==8.1.0pyproject.toml
PyPIpytest-order==1.5.0pyproject.toml
PyPIpytest-playwright==0.9.0pyproject.toml
PyPIpytest-xdist==3.8.0pyproject.toml
PyPItomli>=2.0,<3pyproject.toml
PyPIrequests>=2.33.0,<3pyproject.toml
PyPIpygments>=2.20.0,<3pyproject.toml
PyPIpip>=26.1.2,<27pyproject.toml
PyPImako>=1.3.12,<2pyproject.toml
PyPIidna>=3.15,<4pyproject.toml
PyPIpyyaml>=6.0,<7pyproject.toml
PyPIjupyter-client>=8.0,<9pyproject.toml
PyPIipykernel<8pyproject.toml
PyPInbformat>=5.7,<6pyproject.toml
PyPInbclient>=0.8,<1pyproject.toml
PyPItornado>=6.5.7,<7pyproject.toml
npmastro5.5.5website/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing pypi:posit-vip@2026.8.2 pulls in 69 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.34.0 — full methodology · metrics wiki.

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