object.entries
ES2017 spec-compliant Object.entries shim.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): call-bind is a canonical ljharb/es-shims utility; its addition as a replacement for function-bind+has is a well-known refactoring pattern across this package family. | ai | |
| dependencies | unvetted-dep:define-properties | AI (dependencies): define-properties is a standard es-shims utility maintained by the same author (ljharb); its use here is expected and stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): ljharb's packages consistently lack Sigstore provenance; this is a known pattern for this publisher and not a risk indicator. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.1.9 | 4 / 13 | |
| 1.1.8 | 3 / 13 | |
| 1.1.7 | 3 / 13 | |
| 1.1.6 | 3 / 13 | |
| 1.1.5 | 3 / 11 | |
| 1.1.4 | 3 / 11 | |
| 1.1.3 | 4 / 11 | |
| 1.1.2 | 3 / 10 | |
| 1.1.1 | 4 / 7 | |
| 1.1.0 | 4 / 6 | |
| 1.0.4 | 4 / 8 | |
| 1.0.3 | 4 / 8 | |
| 1.0.2 | 4 / 8 | |
| 1.0.1 | 3 / 8 | |
| 1.0.0 | 3 / 8 |
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.