Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

YamadaBlog/pulse-player

https://github.com/YamadaBlog/pulse-player · scanned 2026-06-16 01:04 UTC (2 months, 1 week ago)

75 raw signals (0 security + 75 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 49 actionable findings from 1 signal source. 26 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
52.4
/100
Security checks
52
0 findings
System graph
52
77.8% cov · 49 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 9 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 49 Crowd 0 Layer: Frontend 3 Security 6 Cicd 5 Quality 35
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 52.4/100 with 77.8% coverage. It contains 717 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 75 findings — concentrated in quality (35), cicd (31), security (6). Risk profile is low: 0 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 30 of 49 actionable findings. 75 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
github/codeql-action/init@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/codeql.yml:42, 51, 54 (3 hits)
.github/workflows/release-please.yml:45
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/pages.yml
.github/workflows/publish-packages.yml
.github/workflows/release-please.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-lib-byte-identical.mjs:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-lib-byte-identical.mjs:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/consumer-smoke.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/consumer-smoke.mjs:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/generate-player-shells.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/generate-player-shells.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/publish-dry-run.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/publish-dry-run.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/registry-guard.mjs:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/registry-guard.mjs:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/setup-demo-audio.mjs:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/setup-demo-audio.mjs:28 Node child process
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 49 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 22 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
9 files, 22 locations
.github/workflows/pages.yml:36, 79, 93, 109, 127 (5 hits)
.github/workflows/a11y.yml:43, 46, 62 (3 hits)
.github/workflows/coverage.yml:41, 44, 57 (3 hits)
.github/workflows/responsive.yml:39, 42, 60 (3 hits)
.github/workflows/visual.yml:29, 32, 54 (3 hits)
.github/workflows/ci.yml:27, 30 (2 hits)
.github/workflows/codeql.yml:39
.github/workflows/consumer-smoke.yml:31
CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/demo-react-native/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/demo-react-native/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/demo-react/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/demo-react/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/demo-svelte/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/demo-svelte/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/01-vite-spa/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/01-vite-spa/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/02-custom-playlist/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/02-custom-playlist/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: examples/03-event-subscriptions/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
examples/03-event-subscriptions/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/angular/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/angular/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/core/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/core/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/react-native/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/react-native/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/react/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/react/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/svelte/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/svelte/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/vue/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/vue/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/web-component/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/web-component/package.json LockfileReproducibilityGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
apps/demo-react-native/package.json CI/CD securitySupply chainNpm
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/demo-react-native/App.tsx:65
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/react/src/PulsePlayer.tsx:29
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — packages/svelte/src/index.ts:26
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/543e9103-0b82-413e-9546-732f2aa7344d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/543e9103-0b82-413e-9546-732f2aa7344d/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.