← Home

object-assign

ES2015 `Object.assign()` ponyfill

17
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

gaearonsindresorhusspicyj

Keywords

objectassignextendpropertieses2015ecmascriptharmonyponyfillprollyfillpolyfillshimbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer addition; spicyj (Ben Alpert) is a known React team member added as co-maintainer by sindresorhus. ai
maintainer-change maintainer-added AI (maintainer-change): spicyj is a well-established npm publisher with strong track record; legitimate co-maintainer addition. ai
publish-pattern dormant-publish AI (publish-pattern): Stable utility package; infrequent publishes are normal for mature, feature-complete ponyfills. ai

Versions (showing 17 of 17)

Version Deps Published
4.1.1 0 / 4
4.1.0 0 / 4
4.0.1 0 / 4
4.0.0 0 / 3
3.0.0 0 / 1
2.1.1 0 / 1
2.0.0 0 / 1
1.0.0 0 / 1
0.4.0 0 / 1
0.3.1 0 / 1
0.3.0 0 / 1
0.2.2 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1

v4.1.0

2 findings
HIGH Publisher changed: sindresorhus → spicyj (on 2016-05-02) provenance

This version was published by a different npm account than previous versions on 2016-05-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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