object-keys 0.3.0
An Object.keys replacement, in case Object.keys is not available. From https://github.com/kriskowal/es5-shim
object-keys@0.3.0 was published on 2013-05-18. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Please update to the latest object-keys
All object-keys versions · Permanent reference to 0.3.0 · Latest release
Package specifications
| Version | 0.3.0 |
|---|---|
| License declaration | MIT |
| Published | 2013-05-18T22:06:13.036Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | 44 |
| Repository forks | 20 |
Install object-keys 0.3.0
npm install object-keys@0.3.0 pnpm add object-keys@0.3.0 yarn add object-keys@0.3.0
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- foreach@2.0.6 — direct
- is@0.2.7 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 0/10 — Found 0/25 approved changesets -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
Evidence and freshness
- https://registry.npmjs.org/object-keys/0.3.0 — retrieved 2026-10-29T11:46:19.789Z
- https://api.deps.dev/v3/projects/github.com%2Fljharb%2Fobject-keys — retrieved 2026-10-29T07:10:29.551Z
- https://api.deps.dev/v3/systems/npm/packages/object-keys/versions/0.3.0:dependencies — retrieved 2026-10-29T11:46:20.678Z
- https://api.deps.dev/v3/systems/npm/packages/object-keys/versions/0.3.0 — retrieved 2026-10-29T11:46:20.656Z