Production-readiness scan · 2026-11-09
sindresorhus/is-plain-obj
Workable, with significant gaps to close.
PARTIAL Dependencies were read from manifests only; transitive packages were not checked.
Security
Secrets, committed configuration and the tooling the repository uses to police itself.
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.
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 — 14 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
- scoring policy: mode=one_shot, model= MiniMax-M3, rubric=d9ea679b9529
- scores adjusted by deterministic evidence: 1 lowered by deterministic ceilings, 1 raised by deterministic floors
Security tooling detected in the repository: security policy