sort-object — Greenflagged

Sort the keys in an object.

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

doowbjonschlinkert

Keywords

arrarrayfunctionjskeykeysobjobjectorderrere-ordersortutilutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): doowb and jonschlinkert are known collaborators; jonschlinkert is listed as maintainer. Legitimate transition from 2016.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance; no security concern for this well-established package.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
3.0.3	6 / 6	2019-09-19
3.0.2	6 / 6	2016-02-03
3.0.1	6 / 2	2016-01-19
3.0.0	6 / 2	2015-07-21
2.0.4	6 / 2	2015-07-09
2.0.3	6 / 2	2015-07-07
2.0.2	5 / 2	2015-06-30
2.0.1	5 / 2	2015-06-30
2.0.0	3 / 2	2015-06-30
1.0.0	2 / 2	2015-01-30
0.3.2	2 / 3	2014-10-24
0.3.1	2 / 3	2014-08-21
0.3.0	3 / 3	2014-08-21
0.2.2	1 / 2	2014-08-15
0.2.1	1 / 2	2014-08-15
0.2.0	1 / 2	2014-08-15
0.0.6	1 / 2	2014-01-31
0.0.5	1 / 2	2013-10-30
0.0.4	1 / 1	2013-10-14
0.0.3	1 / 1	2013-10-14
0.0.2	2 / 1	2013-10-04
0.0.1	0 / 0	2013-10-04

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2016-02-03) provenance

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

v3.0.1

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2016-01-19) provenance

This version was published by a different npm account than previous versions on 2016-01-19. 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.

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.

v2.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.

v2.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.

v2.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.

v2.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.

v2.0.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2015-06-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-06-30. This could indicate a legitimate maintainer transition or an account compromise.