← Home

object.getprototypeof

An ES5 mostly-spec-compliant `Object.getPrototypeOf` sham/polyfill/replacement that works in as many engines as possible

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ljharb

Keywords

Object.getPrototypeOfproto__proto__[[Prototype]]getPrototypeOfES5shimpolyfilles-shim APIbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:call-bind AI (dependencies): call-bind is a well-known ljharb/es-shims ecosystem package; stable dependency for this polyfill. ai
dependencies unvetted-dep:get-proto AI (dependencies): get-proto is a well-known ljharb/es-shims ecosystem package; stable dependency for this polyfill. ai
dependencies unvetted-dep:define-properties AI (dependencies): define-properties is a well-known ljharb/es-shims ecosystem package; stable dependency for this polyfill. ai
dependencies unvetted-dep:reflect.getprototypeof AI (dependencies): reflect.getprototypeof is a well-known ljharb/es-shims ecosystem package; stable dependency for this polyfill. ai
provenance no-provenance AI (provenance): Established package from highly trusted publisher ljharb; absence of Sigstore provenance is not a meaningful risk signal here. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.7 5 / 12
1.0.6 4 / 11
1.0.5 4 / 11
1.0.4 4 / 11
1.0.3 4 / 9
1.0.2 4 / 9
1.0.1 4 / 9
1.0.0 5 / 9

v1.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.