has-proto 1.1.0

Does this environment have the ability to get the [[Prototype]] of an object on creation with `__proto__`?

has-proto@1.1.0 was published on 2024-12-01. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >= 0.4.

All has-proto versions · Permanent reference to 1.1.0 · Latest release

Package specifications

Version1.1.0
License declarationMIT
Published2024-12-01T17:01:33.378Z
Node.js requirement>= 0.4
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size14.22 KiB
Published file count18
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies19
Repository stars6
Repository forks3

Install has-proto 1.1.0

npm install has-proto@1.1.0
pnpm add has-proto@1.1.0
yarn add has-proto@1.1.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.

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.

Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
SAST0/10 — no SAST tool detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness