sindresorhus/array-uniq

scanned 2026-05-18 · git 42335f5

No security issues flagged

🟢 Looks clean so far

Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies—Known OSS vulnerabilities✓Risky code patterns✓Malicious dependencies—Project health10

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ couldn’t run

Packages you depend on that have known security holes (CVEs).

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Trivy v0.58.0 · Apache-2.0

error: 2026-05-18T23:41:33Z FATAL Fatal error init error: DB error: database error: --skip-update cannot be specified on the first run

Known OSS vulnerabilities — OSV-Scannerⓘ none found ✓

Your dependencies cross-checked against the OSV vulnerability database.

Nothing found by this check. ✓

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.95.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ didn’t run

Packages that look intentionally malicious: typosquats, sneaky install scripts.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ 10 notes

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

Worth fixing scorecard-overall OpenSSF Scorecard overall: 3.9/10

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Branch-Protection Branch-Protection scored 0: branch protection not enabled on development/release branches

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-CI-Tests CI-Tests scored 0: 0 out of 4 merged PRs checked by a CI test -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Dependency-Update-Tool Dependency-Update-Tool scored 0: no update tool detected

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Maintained Maintained scored 0: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Pinned-Dependencies Pinned-Dependencies scored 0: dependency not pinned by hash detected -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.
Minor scorecard-Token-Permissions Token-Permissions scored 0: detected GitHub workflow tokens with excessive permissions

A project-health signal (maintenance / supply-chain hygiene), not a vulnerability in your code.

via OpenSSF Scorecard v5.0.0 · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.