Endor Labs Package Score
Evaluate open source package health before adoption.
Input Parsing
Extract from user input:
- Package name (required)
- Version (optional)
- Compare with (optional) - another package for comparison
Workflow
Step 1: Check Vulnerabilities and Risks
Use check_dependency_for_risks MCP tool (preferred — checks vulnerabilities AND malware):
ecosystem: npm, python, go, java, maven, rust, dotnet, ruby, php
dependency_name: package name
version: version to evaluate
Fallback to check_dependency_for_vulnerabilities if _risks unavailable.
Step 2: Get Package Metrics
Use CLI to query from OSS namespace:
# Package version info (always redirect stderr when piping)
npx -y endorctl api list --resource PackageVersion -n oss --filter "meta.name=={ecosystem}://{package}@{version}" 2>/dev/null
# Scorecard (use package UUID from above)
npx -y endorctl api list --resource Metric -n oss --filter "meta.name==package_version_scorecard and meta.parent_uuid=={package_uuid}" 2>/dev/null
Or use get_resource MCP tool:
name: {ecosystem}://{package}@{version}, resource_type: PackageVersion
- Then
resource_type: Metric, name: package_version_scorecard (with package UUID as parent)
Step 3: Present Scores
Present overall score (X/10) with breakdown by category:
| Category |
What it measures |
| Activity |
Commit frequency, last release, contributors, issue response time |
| Popularity |
Downloads, stars, dependents |
| Security |
CVE count, security practices, OSSF scorecard, signed releases, security policy |
| Quality |
Test coverage, documentation, type support, license |
Include vulnerability history table (CVE, severity, fixed version, date).
Recommendation thresholds:
= 8: Recommended for production
- 6-7: Acceptable, monitor
- 4-5: Use with caution, consider alternatives
- < 4: Not recommended
Step 4: Version Comparison (if requested)
Compare CVEs, score, release date across versions.
Step 5: Package Comparison (if requested)
Side-by-side table: overall score, activity, popularity, security, quality, CVE count, license. State recommendation with reasoning.
Next Steps
/endor-check {package} - check vulnerabilities
/endor-upgrade-impact {package} - upgrade analysis
/endor-scan - see impact on your project
For data source policy, read references/data-sources.md.
Error Handling
| Error |
Action |
| Package not found |
Check name/ecosystem. OSS namespace may not have indexed it. Do not use external sites |
| Metrics unavailable |
Package may be too new or small for scoring |
| Auth error |
Run /endor-setup |
1---2name: endor-score3description: >4 Evaluate open source package health before adoption. Use when the user says "should I5 use this package", "is lodash well-maintained", "endor score express", "package health",6 "compare lodash vs underscore", "evaluate this dependency", or wants activity,7 popularity, security, and quality scores. Do NOT use for checking known CVEs in a8 package (/endor-check) or scanning the whole repo (/endor-scan).9metadata:10 source: https://skillmd.com/skills/endorlabs/endor-score11---1213# Endor Labs Package Score1415Evaluate open source package health before adoption.1617## Input Parsing1819Extract from user input:201. **Package name** (required)212. **Version** (optional)223. **Compare with** (optional) - another package for comparison2324## Workflow2526### Step 1: Check Vulnerabilities and Risks2728Use `check_dependency_for_risks` MCP tool (preferred — checks vulnerabilities AND malware):29- `ecosystem`: npm, python, go, java, maven, rust, dotnet, ruby, php30- `dependency_name`: package name31- `version`: version to evaluate3233Fallback to `check_dependency_for_vulnerabilities` if `_risks` unavailable.3435### Step 2: Get Package Metrics3637Use CLI to query from OSS namespace:38```bash39# Package version info (always redirect stderr when piping)40npx -y endorctl api list --resource PackageVersion -n oss --filter "meta.name=={ecosystem}://{package}@{version}" 2>/dev/null4142# Scorecard (use package UUID from above)43npx -y endorctl api list --resource Metric -n oss --filter "meta.name==package_version_scorecard and meta.parent_uuid=={package_uuid}" 2>/dev/null44```4546Or use `get_resource` MCP tool:47- `name`: `{ecosystem}://{package}@{version}`, `resource_type`: `PackageVersion`48- Then `resource_type`: `Metric`, `name`: `package_version_scorecard` (with package UUID as parent)4950### Step 3: Present Scores5152Present overall score (X/10) with breakdown by category:5354| Category | What it measures |55|----------|-----------------|56| Activity | Commit frequency, last release, contributors, issue response time |57| Popularity | Downloads, stars, dependents |58| Security | CVE count, security practices, OSSF scorecard, signed releases, security policy |59| Quality | Test coverage, documentation, type support, license |6061Include vulnerability history table (CVE, severity, fixed version, date).6263**Recommendation thresholds:**64- >= 8: Recommended for production65- 6-7: Acceptable, monitor66- 4-5: Use with caution, consider alternatives67- < 4: Not recommended6869### Step 4: Version Comparison (if requested)7071Compare CVEs, score, release date across versions.7273### Step 5: Package Comparison (if requested)7475Side-by-side table: overall score, activity, popularity, security, quality, CVE count, license. State recommendation with reasoning.7677## Next Steps78791. `/endor-check {package}` - check vulnerabilities802. `/endor-upgrade-impact {package}` - upgrade analysis813. `/endor-scan` - see impact on your project8283For data source policy, read references/data-sources.md.8485## Error Handling8687| Error | Action |88|-------|--------|89| Package not found | Check name/ecosystem. OSS namespace may not have indexed it. Do not use external sites |90| Metrics unavailable | Package may be too new or small for scoring |91| Auth error | Run `/endor-setup` |