Determine if an object is a Buffer without including the full buffer module
93
Pending
Does it follow best practices?
Impact
93%
1.02xAverage score across 9 eval scenarios
Pending
The risk profile of this skill
Non-Buffer type rejection
Package Import
100%
100%
Direct Function Usage
100%
100%
Return Value Usage
100%
100%
No Reimplementation
100%
100%
Buffer type detection
Package import
100%
100%
Core function usage
100%
100%
Direct delegation
100%
100%
Correct return values
100%
100%
Edge case handling for objects with isBuffer properties
is-buffer import
100%
100%
isBuffer function usage
66%
50%
Direct delegation
20%
20%
Edge case handling
60%
60%
No redundant checks
20%
0%
Cross-platform compatibility
is-buffer import
100%
100%
Direct isBuffer usage
100%
100%
Correct return value
100%
100%
No redundant validation
50%
100%
TypeScript definitions
100%
100%
Single responsibility
100%
100%
Minimal performance overhead
Uses is-buffer package
100%
100%
Direct delegation
100%
100%
Minimal wrapping overhead
100%
100%
Correct return value
100%
100%
No redundant checks
100%
100%
Constructor-based validation
Imports is-buffer
100%
100%
Uses is-buffer function
100%
100%
Buffer passthrough logic
100%
100%
Non-Buffer handling
100%
100%
Proper error handling
100%
100%
TypeScript support
Import is-buffer
100%
100%
Use isBuffer function
100%
100%
TypeScript type annotations
100%
100%
Type-safe conditionals
100%
100%
TypeScript compilation
100%
100%
Alternative to Buffer.isBuffer()
Package Import
100%
100%
Core Detection Usage
100%
100%
Result Integration
100%
100%
Logical Application
100%
100%
Null and undefined safety
is-buffer package import
100%
100%
isBuffer implementation uses is-buffer
100%
100%
isBuffer null/undefined safety
100%
100%
isArray null/undefined checks
0%
66%
isPlainObject null/undefined checks
100%
100%
Consistent safety pattern
50%
60%