Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 19:01 UTC

vmware-skills / VMware-NSX-Security

MCP server and CLI for VMware NSX/vDefend firewall policies, security groups, microsegmentation, Traceflow and IDPS operations.

PythonMIT★ 4 stars⑂ 0 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolMCP serverhow this is determined

vmware-skills/VMware-NSX-Security holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Community & Adoption (33/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

vmware-skillsOrganization
15 followers16 public repossince Aug 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIvmware-nsx-security1.17.41,059832 days agoai-opsdfwfirewallmcpmicrosegmentationnsxnsx-tvmware

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 recency — last push 2 days ago
18.7/36Commit cadence — 27/52 weeks with commits
18/18Commit volume — 190 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_year190
human_commit_share0.98
days_since_last_push2
active_weeks_last_year27
How it's scored
27/27Ships releases — 82 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~6.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count82
latest_release_tagv1.17.4
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases6.8

Community & Adoption

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

33At Risk · 17% of overall
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
40.3/80Monthly downloads — 1,059 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvmware-nsx-security
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,059
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
21.6/30PR acceptance — 23/32 decided PRs merged
13/13Newcomer PR acceptance — 16/16 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues0
closed_issues4
prs_merged_7d3
prs_decided_7d3
prs_merged_30d16
prs_decided_30d16
issue_closed_ratio1
closed_unmerged_prs9
first_time_authors_30d1
first_time_prs_merged_30d16
first_time_prs_decided_30d16
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
8.7/25Owner reach — 15 followers of vmware-skills
9.6/25Track record — 16 public repos, account ~0 yr old
Inputs used
followers15
owner_typeOrganization
is_verifiedno
owner_loginvmware-skills
public_repos16
account_age_days112

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 2 days ago
20/20Version history — 83 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvmware-nsx-security
ecosystemspypi
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/vmware-skills/marketplace
10/10Repository description
10/10Topics — 15 topics
10/10Wiki
Inputs used
topicsagent-skills, ai-skill, claude-code, codex, dfw, firewall, gemini-cli, mcp, nsx, security, vmware, gemini-cli-extension, mcp-server, python, vsphere
has_wikiyes
homepagehttps://github.com/vmware-skills/marketplace
docs_sitehttps://github.com/vmware-skills/marketplace
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection. 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
advisories0
affected_packages0
assessed_packages50
unassessed_packages0
affected_by_severitynone
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 50 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 94 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.959
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 36 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.36
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/83 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes45,608
source_files_sampled83
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

4GitHub stars
1contributors
190commits, last 12 months
2days since last push
82releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'vmware-nsx-security-mcpb' from its registry
  • deps.dev does not index pypi:vmware-nsx-security@1.17.4; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-11-21 19:00 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/26 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
PyPIvmware-nsx-security==1.17.4mcpb/pyproject.toml
PyPIhttpx>=0.27,<1.0pyproject.toml
PyPItyper>=0.12,<1.0pyproject.toml
PyPIrich>=13.0,<15.0pyproject.toml
PyPIpyyaml>=6.0,<7.0pyproject.toml
PyPIpython-dotenv>=1.0,<2.0pyproject.toml
PyPImcp>=1.30,<2.0pyproject.toml
PyPIvmware-policy>=1.26.0,<2.0pyproject.toml
All dependencies 50

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

RegistryPackageVersionRelation
PyPIhttpx0.28.1direct
PyPImcp1.30.0direct
PyPIpython-dotenv1.2.2direct
PyPIpyyaml6.0.3direct
PyPIrich14.3.3direct
PyPItyper0.24.1direct
PyPIvmware-nsx-security1.17.4direct
PyPIvmware-policy1.26.0direct
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.15.1indirect
PyPIattrs26.1.0indirect
PyPIcertifi2026.10.19indirect
PyPIcffi2.0.0indirect
PyPIclick8.3.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.5indirect
PyPIcryptography50.0.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx-sse0.4.3indirect
PyPIidna3.15indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImarkdown-it-py4.0.0indirect
PyPImdurl0.1.2indirect
PyPIpackaging26.2indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.12.5indirect
PyPIpydantic-core2.41.5indirect
PyPIpydantic-settings2.14.2indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.15.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-multipart0.0.32indirect
PyPIpywin32311indirect
PyPIreferencing0.37.0indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.15.12indirect
PyPIshellingham1.5.4indirect
PyPIsse-starlette3.3.4indirect
PyPIstarlette1.3.1indirect
PyPItomli2.4.1indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.2indirect
PyPIuvicorn0.42.0indirect
Dependency advisories 0

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

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