Security Deep Dive
converse.js
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects v14.0.0.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
3d stale
scorecard
1.84 / 4.0
Score 4.6/10
cve health
1.75 / 2.5
No open CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-0.66 / 10.0
Risk 6.5/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
7.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.3
10%
Provenance trust
provenance trust
4.6
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 6.5/100Scorecard
Scorecard 4.6/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Packaging | -1 | packaging workflow not detected |
| Maintained | 10 | 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 0 | Found 1/30 approved changesets -- score normalized to 0 |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0 | security policy file not detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| License | 10 | license file detected |
| Pinned-Dependencies | 2 | dependency not pinned by hash detected -- score normalized to 2 |
| Branch-Protection | -1 | internal 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 |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| SAST | 10 | SAST tool is run on all commits |
| Fuzzing | 0 | project is not fuzzed |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
1
High
1
Medium
0
Low
0
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2025-7783 | critical | — | form-data | 4.0.2 | v13.0.0 |
| CVE-2022-37620 | high | — | html-minifier | 4.0.0 | v13.0.0 |
Showing 2 of 2