Public recordGood
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-31 17:33 UTC
deploymenttheory / go-sdk-jamfpro-v2
A community Jamf Pro sdk v2 for classic and jamf pro api's, written in go. With full api surface coverage
deploymenttheory/go-sdk-jamfpro-v2 holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.
78
overall / 100Software 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.
78
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)
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).
Ownership
Deployment TheoryOrganization
30 followers49 public repossince Apr 2022
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| Go | github.com/deploymenttheory/go-sdk-jamfpro-v2 | v0.16.0 | - | 20 | 11 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
88
Development activity
80Excellent
How it's scored
| 36/36 | Push recency — last push 2 days ago |
| 15.9/36 | Commit cadence — 23/52 weeks with commits |
| 18/18 | Commit volume — 400 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 400 |
| human_commit_share | 0.68 |
| days_since_last_push | 2 |
| active_weeks_last_year | 23 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 20 releases published |
| 36/36 | Release recency — latest release 11 days ago |
| 27/27 | Release cadence — a release every ~14.6 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 20 |
| latest_release_tag | v0.16.0 |
| releases_from_tags | no |
| days_since_latest_release | 11 |
| mean_days_between_releases | 14.6 |
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?
43
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 1 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 1 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
92Excellent
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | yes |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
53
Maintainer resilience (bus factor)
13Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 3/10 | OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
Issue & PR responsiveness
54Moderate
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 24.3/30 | PR acceptance — 148/183 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/8 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 148 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | — |
| closed_unmerged_prs | 35 |
| 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.
Ownership & stewardship
62Moderate
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 10.7/25 | Owner reach — 30 followers of deploymenttheory |
| 21/25 | Track record — 49 public repos, account ~4 yr old |
Inputs used
| followers | 30 |
| owner_type | Organization |
| is_verified | — |
| owner_login | deploymenttheory |
| public_repos | 49 |
| account_age_days | 1,575 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 35/35 | Publish recency — latest publish 11 days ago |
| 20/20 | Version history — 20 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/deploymenttheory/go-sdk-jamfpro-v2 |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 11 |
Engineering Quality
Are baseline engineering and documentation practices in place?
84
Engineering practices
84Excellent
How it's scored
| 24/24 | CI workflows — 8 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .golangci.yml |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
85Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 4 topics |
| 10/10 | Wiki |
Inputs used
| topics | jamf, golang, jamfpro, sdk-go |
| has_wiki | yes |
| homepage | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
62
Security posture
52Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 3.8/7.5 | Branch-Protection — branch protection is not maximal on development and all release branches |
| 2.5/2.5 | CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/8 approved changesets -- score normalized to 0 |
| 0.8/2.5 | Contributors — project has 1 contributing companies or organizations -- score normalized to 3 |
| 0/10 | Dangerous-Workflow — dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 5/5 | Pinned-Dependencies — all dependencies are pinned |
| 5/5 | SAST — SAST tool is run on all commits |
| 4.5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 1.5/7.5 | Vulnerabilities — 8 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5.2 |
Excluded from scoring (no data or not applicable): packaging, signed_releases. Remaining weights renormalized.
Dependency advisories
100Exceptional
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 0/25 | Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 9 |
| affected_packages | 1 |
| assessed_packages | 42 |
| unassessed_packages | 0 |
| affected_by_severity | moderate 1 |
| direct_affected_packages | 0 |
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 42 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.
76
Agent context & guidance
40Weak
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 68 of 68 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| legible_history_share | 1 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
93Exceptional
How it's scored
| 12.6/18 | One-command bootstrap — go.mod, tools/doc_url_tester/go.mod, tools/function_auditor/go.mod (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .golangci.yml |
| 11/11 | Static type checking — Go (statically typed) |
| 10/10 | Reproducible environment — lockfile |
| 8/10 | Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited |
| 8/8 | Automated maintenance — 32 of the last 100 commits are automated dependency updates |
| 10/10 | OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0.04 |
| toolchain_manifests | go.mod, tools/doc_url_tester/go.mod, tools/function_auditor/go.mod |
| dependency_bot_commit_share | 0.32 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Go (statically typed) |
| 55/55 | Manageable file sizes — 0/1,600 source files over 60KB |
Inputs used
| primary_language | Go |
| largest_source_bytes | 48,337 |
| source_files_sampled | 1,600 |
| oversized_source_files | 0 |
Machine-readable interfaces
80Excellent
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — openapi-specs/11.23.2-t1767621885710/swagger.yaml, openapi-specs/11.25.2-t1772925731845/swagger.yaml, openapi-specs/11.26.1-t1774880441315/swagger.yaml, openapi-specs/11.27.0-t1776264729651/swagger.yaml, openapi-specs/11.27.1-t1777388207638/swagger.yaml, openapi-specs/11.28.0-t1778099559180/swagger.yaml, openapi-specs/11.28.1-t1779801919649/swagger.yaml, openapi-specs/11.29.1-t1782156420899/swagger.yaml, openapi-specs/11.30.0-t1782920582649/swagger.yaml |
| 0/20 | MCP server |
| 40/40 | Runnable examples — examples, recipes |
Inputs used
| example_dirs | examples, recipes |
| has_mcp_signal | no |
| api_schema_files | openapi-specs/11.23.2-t1767621885710/swagger.yaml, openapi-specs/11.25.2-t1772925731845/swagger.yaml, openapi-specs/11.26.1-t1774880441315/swagger.yaml, openapi-specs/11.27.0-t1776264729651/swagger.yaml, openapi-specs/11.27.1-t1777388207638/swagger.yaml, openapi-specs/11.28.0-t1778099559180/swagger.yaml, openapi-specs/11.28.1-t1779801919649/swagger.yaml, openapi-specs/11.29.1-t1782156420899/swagger.yaml, openapi-specs/11.30.0-t1782920582649/swagger.yaml |
Key facts
1GitHub stars
1contributors
400commits, last 12 months
2days since last push
20releases
1bus factor
0open issues
Gopackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
OpenSSF Scorecard 5.2 / 10
5.2aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 5 | Branch-Protection | branch protection is not maximal on development and all release branches |
| 10 | CI-Tests | 14 out of 14 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/8 approved changesets -- score normalized to 0 |
| 3 | Contributors | project has 1 contributing companies or organizations -- score normalized to 3 |
| 0 | Dangerous-Workflow | dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 10 | Pinned-Dependencies | all dependencies are pinned |
| 10 | SAST | SAST tool is run on all commits |
| 9 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 2 | Vulnerabilities | 8 existing vulnerabilities detected |
Direct dependencies 13
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | github.com/aws/aws-sdk-go-v2 | v1.43.0 | go.mod |
| Go | github.com/aws/aws-sdk-go-v2/config | v1.32.31 | go.mod |
| Go | github.com/aws/aws-sdk-go-v2/credentials | v1.19.30 | go.mod |
| Go | github.com/aws/aws-sdk-go-v2/feature/s3/manager | v1.22.35 | go.mod |
| Go | github.com/aws/aws-sdk-go-v2/service/s3 | v1.106.0 | go.mod |
| Go | github.com/stretchr/testify | v1.11.1 | go.mod |
| Go | go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp | v0.69.0 | go.mod |
| Go | go.opentelemetry.io/otel | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/exporters/stdout/stdouttrace | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/sdk | v1.44.0 | go.mod |
| Go | go.uber.org/zap | v1.28.0 | go.mod |
| Go | howett.net/plist | v1.0.1 | go.mod |
| Go | resty.dev/v3 | v3.0.0-rc.3 | go.mod |
All dependencies 42
Full resolved dependency set from the GitHub dependency graph: 13 direct and 29 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Go | github.com/aws/aws-sdk-go-v2 | v1.43.0 | direct |
| Go | github.com/aws/aws-sdk-go-v2/config | v1.32.31 | direct |
| Go | github.com/aws/aws-sdk-go-v2/credentials | v1.19.30 | direct |
| Go | github.com/aws/aws-sdk-go-v2/feature/s3/manager | v1.22.35 | direct |
| Go | github.com/aws/aws-sdk-go-v2/service/s3 | v1.106.0 | direct |
| Go | github.com/stretchr/testify | v1.11.1 | direct |
| Go | go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp | v0.69.0 | direct |
| Go | go.opentelemetry.io/otel | v1.44.0 | direct |
| Go | go.opentelemetry.io/otel/exporters/stdout/stdouttrace | v1.44.0 | direct |
| Go | go.opentelemetry.io/otel/sdk | v1.44.0 | direct |
| Go | go.uber.org/zap | v1.28.0 | direct |
| Go | howett.net/plist | v1.0.1 | direct |
| Go | resty.dev/v3 | v3.0.0-rc.3 | direct |
| Go | github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream | v1.7.14 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/feature/ec2/imds | v1.18.31 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/internal/configsources | v1.4.31 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 | v2.7.31 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/internal/v4a | v1.4.32 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding | v1.13.13 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/internal/checksum | v1.9.24 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/internal/presigned-url | v1.13.31 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/internal/s3shared | v1.19.32 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/signin | v1.5.0 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/sso | v1.33.0 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/ssooidc | v1.38.0 | indirect |
| Go | github.com/aws/aws-sdk-go-v2/service/sts | v1.45.0 | indirect |
| Go | github.com/aws/smithy-go | v1.27.3 | indirect |
| Go | github.com/cespare/xxhash/v2 | v2.3.0 | indirect |
| Go | github.com/davecgh/go-spew | v1.1.1 | indirect |
| Go | github.com/felixge/httpsnoop | v1.0.4 | indirect |
| Go | github.com/go-logr/logr | v1.4.3 | indirect |
| Go | github.com/go-logr/stdr | v1.2.2 | indirect |
| Go | github.com/google/uuid | v1.6.0 | indirect |
| Go | github.com/pmezard/go-difflib | v1.0.0 | indirect |
| Go | go.opentelemetry.io/auto/sdk | v1.2.1 | indirect |
| Go | go.opentelemetry.io/otel/metric | v1.44.0 | indirect |
| Go | go.opentelemetry.io/otel/trace | v1.44.0 | indirect |
| Go | go.uber.org/multierr | v1.11.0 | indirect |
| Go | golang.org/x/net | v0.49.0 | indirect |
| Go | golang.org/x/sys | v0.45.0 | indirect |
| Go | golang.org/x/time | v0.14.0 | indirect |
| Go | gopkg.in/yaml.v3 | v3.0.1 | indirect |
Dependency advisories 1
This repository publishes no package the index resolves, so its own dependency graph was assessed — 42 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| golang.org/x/net | v0.49.0 | indirect | moderate | 9 | 1.26.3 |
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
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.5.0, schema v0.27.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go.