Public record
Software health reportschema 0.32.0 · metrics 2.10.0 · 2026-08-20 10:42 UTC

packagist / bitbucket-api

Simple Bitbucket API wrapper for PHP

PHPMIT★ 1 star⑂ 2 forkssince Jun 2021forkView on GitHub ↗

packagist/bitbucket-api holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (67/100) and lowest on Community & Adoption (22/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

41 followers20 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistprivate-packagist/bitbucket-api2.3.05,54629421 days agoapibitbucket

Metrics by category

Vitality

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

51Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
6/10OpenSSF Scorecard: Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push0
active_weeks_last_year0
How it's scored
16.2/27Ships releases30 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
5.4/27Release cadencea release every ~376 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count30
latest_release_tag2.4.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases376
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?

22At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
49.9/80Monthly downloads5,546 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesprivate-packagist/bitbucket-api
dependents0
ecosystemspackagist
total_downloads108,962
monthly_downloads5,546
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.4/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth18 contributors
10/10OpenSSF Scorecard: Contributorsproject has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.805
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance19/19 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/12 approved changesets -- score normalized to 0
Inputs used
merged_prs19
open_issues0
closed_issues1
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs0
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 domainverified-domain status not read for this organization
11.7/25Owner reach41 followers of packagist
21.6/25Track record20 public repos, account ~9 yr old
Inputs used
followers41
owner_typeOrganization
is_verified
owner_loginpackagist
public_repos20
account_age_days3,614
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 421 days ago
20/20Version history29 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesprivate-packagist/bitbucket-api
ecosystemspackagist
any_deprecatedno
min_days_since_publish421

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests3 out of 10 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests3 out of 10 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
0/7.5Code-ReviewFound 0/12 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 7 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
4.5/7.5Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.7/40Legible commit history35 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.35
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/97 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes11,364
source_files_sampled97
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, examples
Inputs used
example_dirsexample, examples
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

1GitHub stars
18contributors
0commits, last 12 months
0days since last push
30releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks

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.

111222212022-012022-052022-09
OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-20 10:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests3 out of 10 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/12 approved changesets -- score normalized to 0
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Packagistpsr/http-message^1.0 || ^2.0composer.json
Packagistsymfony/deprecation-contracts^2.2 || ^3.0composer.json
Packagistpsr/http-factory-implementation^1.0composer.json
All dependencies 15

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

RegistryPackageVersionRelation
Packagistpsr/http-factory-implementationdirect
Packagistpsr/http-messagedirect
Packagistsymfony/deprecation-contractsdirect
Packagistext-jsonindirect
Packagistnyholm/psr7indirect
Packagistphpindirect
Packagistphp-http/client-commonindirect
Packagistphp-http/client-implementationindirect
Packagistphp-http/discoveryindirect
Packagistphp-http/httplugindirect
Packagistphp-http/message-factoryindirect
Packagistphp-http/mock-clientindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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