@stdlib/assert-is-boolean

This package does exactly what it says: checks if a value is a boolean. The API is straightforward with `isBoolean(value)` returning true for boolean primitives and `isBoolean.isObject(value)` for Boolean objects. TypeScript definitions work as expected, and the function handles edge cases correctly.

The main issue is that this is part of the @stdlib ecosystem, which means you're pulling in a package for something trivially implemented as `typeof value === 'boolean'`. The package itself has dependencies on other @stdlib packages, adding unnecessary weight to your node_modules. For such a simple utility, the cognitive overhead of managing another dependency doesn't justify the marginal benefit of explicit naming.

That said, the documentation is thorough with good examples, and if you're already deeply invested in the stdlib ecosystem for statistical computing or scientific applications, the consistency might be valuable. The error messages are non-existent since it never throws, which is appropriate for a predicate function.

This is a straightforward utility that does exactly what it says: checks if a value is a boolean primitive or Boolean object. In practice, it's incredibly predictable—returns true for `true`, `false`, `new Boolean(true)`, and `new Boolean(false)`, and false for everything else. No surprises, no edge cases that catch you off guard.

From a security perspective, this is as low-risk as dependencies get. It's a pure utility function with no I/O, no network calls, no file system access. The implementation is simple enough to audit in seconds, and being part of the stdlib ecosystem means consistent maintenance and CVE response patterns. Zero dependencies means zero transitive supply chain risk, which is refreshing in the npm ecosystem.

The only real consideration is whether you need a dependency for this at all—it's essentially a wrapper around `typeof x === 'boolean' || x instanceof Boolean`. For security-critical codebases where minimizing attack surface matters, this is negligible overhead with clear, testable behavior.

This package does exactly what it says: checks if a value is a boolean. The API is straightforward with `isBoolean()` and `isBoolean.isPrimitive()` / `isBoolean.isObject()` for distinguishing primitives from Boolean objects. Documentation is clear with examples, and error messages are reasonable when you pass incorrect arguments.

The main concern is whether you need a dependency for this at all. The learning curve is non-existent because it's a single function, but that simplicity also raises questions about value-add. For primitive booleans, `typeof x === 'boolean'` works fine. The package shines slightly when you need to detect Boolean objects (`new Boolean(true)`), but those are rare in modern JavaScript and generally considered an anti-pattern.

Community support is limited given the narrow scope - you won't find many Stack Overflow discussions because there's little to discuss. The stdlib ecosystem is well-maintained overall, but for such a trivial check, adding a dependency feels like overkill unless you're already committed to the stdlib suite of utilities.