Trust and health report
soloud - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 3w · GitHub synced 3w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 716d ago · last release 6y
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 11425189
- Not a fork
- Personal account
- Computed 3w
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
No lockfile (source not queried)- Last query
- 1mo
- Scanner
- osv@v1
deps.dev advisories
No lockfile (source not queried)- Last query
- 1mo
- Scanner
- deps.dev@v1
OpenSSF Scorecard
Published findings- Last query
- 1mo
- Scanner
- openssf-scorecard@v1
- Stored findings
- 12
Weekly public scans omit some checks at scale.
View source evidenceOpenSSF Scorecard checks
Code-Review (2/10): Found 7/24 approved changesets -- score normalized to 2
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#code-reviewDangerous-Workflow (-1/10): no workflows found
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#dangerous-workflowPackaging (-1/10): packaging workflow not detected
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#packagingMaintained (0/10): 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#maintainedToken-Permissions (-1/10): No tokens found
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#token-permissionsPinned-Dependencies (-1/10): no dependencies found
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#pinned-dependenciesSecurity-Policy (0/10): security policy file not detected
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#security-policyFuzzing (0/10): project is not fuzzed
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#fuzzingSigned-Releases (-1/10): no releases found
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#signed-releasesBranch-Protection (0/10): branch protection not enabled on development/release branches
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#branch-protectionCII-Best-Practices (0/10): no effort to earn an OpenSSF best practices badge detected
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#cii-best-practicesSAST (0/10): SAST tool is not run on all commits -- score normalized to 0
https://github.com/ossf/scorecard/blob/916bfc57fa7431467a33a5a013cba3f8a0c1ec50/docs/checks.md#sastMethod and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/jarikomppa-soloud/trust.
Common questions
- Is soloud maintained?
- GraphCanon rates soloud "Dormant" (18% maintenance signal from public GitHub metadata, computed 3w). Last push was 716 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is soloud safe to use?
- Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify soloud as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is soloud a fork?
- No. soloud is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does soloud have known security vulnerabilities?
- Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the soloud trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 3w (methodology github_public_v1).
- What does GraphCanon never claim about soloud?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for soloud. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for soloud?
- 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 for full scope and limits.