Public recordModerate
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 23:27 UTC
contful / contful-enterprise
Contful Enterprise Edition - 企业级 Headless CMS
contful/contful-enterprise holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Security (32/100). It was last updated 67 days ago.
63
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.
63
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 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02).
Ownership
ContfulOrganization
1 follower2 public repossince Nov 2023
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/contful/contful-enterprise | v1.6.7 | - | 3 | 72 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
65
Development activity
50Moderate
How it's scored
| 18/36 | Push recency — last push 67 days ago |
| 9/36 | Commit cadence — 13/52 weeks with commits |
| 18/18 | Commit volume — 439 commits in the last year |
| 5/10 | OpenSSF Scorecard: Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
Inputs used
| commits_last_year | 439 |
| human_commit_share | 1 |
| days_since_last_push | 67 |
| active_weeks_last_year | 13 |
Release discipline
88Excellent
How it's scored
| 16.2/27 | Ships releases — 3 version tags (no GitHub releases) |
| 36/36 | Release recency — latest release 72 days ago |
| 27/27 | Release cadence — a release every ~25.5 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 3 |
| latest_release_tag | v1.6.7 |
| releases_from_tags | yes |
| days_since_latest_release | 72 |
| mean_days_between_releases | 25.5 |
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 (Apache-2.0) |
| 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 | 4 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | shields.io |
| has_pull_request_template | yes |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
67
How it's scored
| 42/42 | Issue resolution — 100% of issues closed |
| 0/30 | PR acceptance — no decided pull requests or no data |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 0 |
| open_issues | 0 |
| closed_issues | 29 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 1 |
| closed_unmerged_prs | 0 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
41Weak
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 2.2/25 | Owner reach — 1 followers of contful |
| 9.2/25 | Track record — 2 public repos, account ~2 yr old |
Inputs used
| followers | 1 |
| owner_type | Organization |
| is_verified | no |
| owner_login | contful |
| public_repos | 2 |
| account_age_days | 1,047 |
Package maintenance
92Excellent
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 35/35 | Publish recency — latest publish 72 days ago |
| 12/20 | Version history — 3 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/contful/contful-enterprise |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 72 |
Engineering Quality
Are baseline engineering and documentation practices in place?
78
Engineering practices
80Excellent
How it's scored
| 24/24 | CI workflows — 3 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — eslint.config.js |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
Documentation
75Good
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| 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?
32
Security posture
32At Risk
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 0/2.5 | Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 3.8/7.5 | Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — no SAST tool detected |
| 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 |
| 0/7.5 | Vulnerabilities — 34 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 3.2 |
Excluded from scoring (no data or not applicable): CI-Tests, 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.
60
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 — 97 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.97 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 12.6/18 | One-command bootstrap — admin/go.mod, openapi/go.mod, shared/go.mod (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — eslint.config.js |
| 11/11 | Static type checking — console/tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum, yarn.lock |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | console/tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | admin/go.mod, openapi/go.mod, shared/go.mod |
| dependency_bot_commit_share | 0 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Go (statically typed) |
| 55/55 | Manageable file sizes — 0/178 source files over 60KB |
Inputs used
| primary_language | Go |
| largest_source_bytes | 32,870 |
| source_files_sampled | 178 |
| oversized_source_files | 0 |
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — conf/openapi.yaml |
| 0/20 | MCP server |
| 0/40 | Runnable examples |
Inputs used
| example_dirs | — |
| has_mcp_signal | no |
| api_schema_files | conf/openapi.yaml |
| interfaces_expected_of | network-service |
Key facts
1GitHub stars
-contributors
439commits, last 12 months
67days since last push
3releases
-bus factor
0open issues
Go, npmpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Contributor list unavailable
- Could not fetch go package 'github.com/contful/contful/admin' from its registry
- Could not fetch go package 'github.com/contful/contful/openapi' from its registry
- Could not fetch npm package 'contful-console' from its registry
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 3.2 / 10
3.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 |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 0 | Contributors | project has 0 contributing companies or organizations -- score normalized to 0 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 5 | Maintained | 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | no SAST tool detected |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 0 | Vulnerabilities | 34 existing vulnerabilities detected |
Direct dependencies 51
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | gitee.com/chunanyong/dm | v1.8.23 | admin/go.mod |
| Go | github.com/aliyun/alibabacloud-oss-go-sdk-v2 | v1.5.2 | admin/go.mod |
| Go | github.com/aws/aws-sdk-go-v2 | v1.42.1 | admin/go.mod |
| Go | github.com/aws/aws-sdk-go-v2/config | v1.32.29 | admin/go.mod |
| Go | github.com/aws/aws-sdk-go-v2/credentials | v1.19.28 | admin/go.mod |
| Go | github.com/aws/aws-sdk-go-v2/service/s3 | v1.105.0 | admin/go.mod |
| Go | github.com/gin-gonic/gin | v1.12.0 | admin/go.mod |
| Go | github.com/golang-jwt/jwt/v5 | v5.3.1 | admin/go.mod |
| Go | github.com/huaweicloud/huaweicloud-sdk-go-obs | v3.26.3+incompatible | admin/go.mod |
| Go | github.com/jackc/pgx/v5 | v5.10.0 | admin/go.mod |
| Go | github.com/pquerna/otp | v1.5.0 | admin/go.mod |
| Go | github.com/redis/go-redis/v9 | v9.21.0 | admin/go.mod |
| Go | github.com/robfig/cron/v3 | v3.0.1 | admin/go.mod |
| Go | github.com/rs/zerolog | v1.35.1 | admin/go.mod |
| Go | github.com/spf13/viper | v1.21.0 | admin/go.mod |
| Go | github.com/subosito/gotenv | v1.6.0 | admin/go.mod |
| Go | github.com/tencentyun/cos-go-sdk-v5 | v0.7.74 | admin/go.mod |
| Go | github.com/tjfoc/gmsm | v1.4.1 | admin/go.mod |
| Go | golang.org/x/crypto | v0.54.0 | admin/go.mod |
| Go | gopkg.in/yaml.v3 | v3.0.1 | admin/go.mod |
| Go | gorm.io/datatypes | v1.2.7 | admin/go.mod |
| Go | gorm.io/gorm | v1.31.2 | admin/go.mod |
| Go | github.com/contful/contful-enterprise/shared | v0.0.0 | admin/go.mod |
| Go | github.com/fsnotify/fsnotify | v1.10.1 | admin/go.mod |
| npm | @tinymce/tinymce-vue | ^6.3.0 | console/package.json |
| npm | @tiptap/starter-kit | ^3.27.3 | console/package.json |
| npm | @tiptap/vue-3 | ^3.27.3 | console/package.json |
| npm | @vue/compiler-sfc | ^3.5.39 | console/package.json |
| npm | axios | ^1.18.1 | console/package.json |
| npm | jsencrypt | ^3.5.4 | console/package.json |
| npm | pinia | ^3.0.4 | console/package.json |
| npm | sm-crypto | ^0.4.0 | console/package.json |
| npm | tdesign-vue-next | ^1.20.3 | console/package.json |
| npm | tinymce | ^8.7.0 | console/package.json |
| npm | vue | ^3.5.39 | console/package.json |
| npm | vue-i18n | ^11.4.6 | console/package.json |
| npm | vue-json-pretty | ^2.6.0 | console/package.json |
| npm | vue-router | 5.1.0 | console/package.json |
| Go | github.com/gin-gonic/gin | v1.12.0 | openapi/go.mod |
| Go | github.com/graphql-go/graphql | v0.8.1 | openapi/go.mod |
| Go | github.com/graphql-go/handler | v0.2.4 | openapi/go.mod |
| Go | github.com/redis/go-redis/v9 | v9.21.0 | openapi/go.mod |
| Go | github.com/rs/zerolog | v1.35.1 | openapi/go.mod |
| Go | github.com/spf13/viper | v1.21.0 | openapi/go.mod |
| Go | github.com/subosito/gotenv | v1.6.0 | openapi/go.mod |
| Go | gorm.io/gorm | v1.31.2 | openapi/go.mod |
| Go | github.com/contful/contful-enterprise/shared | v0.0.0 | openapi/go.mod |
| Go | gitee.com/chunanyong/dm | v1.8.18 | shared/go.mod |
| Go | github.com/google/uuid | v1.6.0 | shared/go.mod |
| Go | gorm.io/driver/postgres | v1.6.0 | shared/go.mod |
| Go | gorm.io/gorm | v1.31.1 | shared/go.mod |
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
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.
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 — Go.