sindresorhus/is-plain-obj
— /100
// permalink — this URL always shows scan
// a newer public scan exists: www.codeclanker.com/scan/sindresorhus/is-plain-obj
kh_1lkM2 from 2026-09-07, even if a newer public scan exists for this repo.// a newer public scan exists: www.codeclanker.com/scan/sindresorhus/is-plain-obj
Security
Secrets, committed configuration and the tooling the repository uses to police itself.
medium
No lockfile committed
Dependency versions are declared as ranges, so two installs can resolve to different code and transitive dependencies could not be checked at all. Commit the lockfile your package manager produces.
medium
No start command is declared anywhere
The repository has a server entrypoint but no start script, Procfile, Docker CMD or platform config saying how to run it. Buildpacks guess, and guess differently from each other, so the first deploy either starts the wrong process or none at all.
index.js
What was scanned
- every file scanned for secrets — 15 in total, none skipped
- 3 dependencies from manifests only — no lockfile, transitive deps unchecked
- deploy checks read 4 shipping file(s), 0 bind site(s) and 0 environment variable(s)
- code quality parsed 4 source file(s), 125 lines, ESLint over 4
- the AI scored from manifests and the file tree; it did not read source itself
Security tooling detected in the repository: security policy