---
title: "process-compose trust report"
type: "trust-report"
slug: "f1bonacc1-process-compose"
canonical_url: "https://www.graphcanon.com/tools/f1bonacc1-process-compose/trust"
computed_at: "2026-07-15T10:51:30.484Z"
maintenance_label: "Very active"
security_status: "findings"
---

# process-compose trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Very active (96% recency signal)
- Days since last push: 3
- Last release: 2026-07-11T19:39:10Z
- Releases (90d): 3
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 478293508
- Not a fork
- Owner type: User
- Computed at: 2026-07-15T10:51:30.484Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: Published findings
  - Last query: 2026-07-15T10:51:32.459732+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/F1bonacc1/process-compose
  - Note: Weekly public scans omit some checks at scale.

### Findings

- **low**: GHSA-4f99-4q7p-p3gh (github.com/sirupsen/logrus@v1.4.2 · go.sum · osv@v1)
- **low**: GO-2025-4188 (github.com/sirupsen/logrus@v1.4.2 · go.sum · osv@v1)
- **low**: GO-2026-5932 (golang.org/x/crypto@v0.53.0 · go.sum · osv@v1)

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is process-compose maintained?

GraphCanon rates process-compose "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 3 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is process-compose safe to use?

Last scanned today (deps profile). Status: 3 low - 3 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify process-compose as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is process-compose a fork?

No. process-compose is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does process-compose have known security vulnerabilities?

Last scanned today (deps profile). Status: 3 low - 3 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

### How often is the process-compose trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

### What does GraphCanon never claim about process-compose?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for process-compose. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for process-compose?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read [trust methodology](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/f1bonacc1-process-compose/trust`](/api/graphcanon/tools/f1bonacc1-process-compose/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_