traverse MIT 40 versions

traverse

npm Repository Homepage

traverse and transform objects by visiting every node on a recursive walk

40

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

traversewalkrecursivemapforEachdeepclone

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition from substack to ljharb, a highly trusted npm maintainer who routinely adopts unmaintained packages.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): ljharb and nopersonsmodules added as part of well-known package adoption pattern by ljharb.	ai	2026/04/24
provenance	no-provenance	AI (provenance): No provenance is low severity; package is otherwise well-established with trusted publisher.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): New deps (gopd, typedarray.prototype.slice, which-typed-array) are legitimate ljharb-maintained utilities consistent with adding typed array support to traverse. No malicious signal.	ai	2026/04/24
dependencies	unvetted-dep:gopd	AI (dependencies): gopd is a well-known ljharb utility package widely used across the ecosystem; stable false positive for this package.	ai	2026/04/23

Versions (showing 40 of 40)

Version	Deps	Published
0.6.11	3 / 9	2025-01-16
0.6.10	3 / 9	2024-09-13
0.6.9	3 / 9	2024-04-09
0.6.8	0 / 9	2023-12-20
0.6.7	0 / 8	2022-10-13
0.6.6	0 / 1	2013-09-24
0.6.5	0 / 2	2013-08-30
0.6.3	0 / 1	2012-06-19
0.6.2	0 / 1	2012-06-16
0.6.1	0 / 1	2012-04-07
0.6.0	0 / 1	2012-02-21
0.5.2	0 / 1	2011-10-16
0.5.1	0 / 1	2011-08-23
0.5.0	0 / 1	2011-08-23
0.4.6	0 / 1	2011-07-28
0.4.5	0 / 1	2011-07-24
0.4.4	0 / 1	2011-07-20
0.4.3	0 / 1	2011-06-15
0.4.2	0 / 1	2011-06-11
0.4.1	0 / 1	2011-06-11
0.4.0	0 / 1	2011-06-11
0.3.9	0 / 1	2011-06-15
0.3.8	0 / 1	2011-06-07
0.3.7	0 / 1	2011-06-06
0.3.6	0 / 2	2011-06-03
0.3.5	0 / 2	2011-05-29
0.3.4	0 / 2	2011-04-17
0.3.3	0 / 2	2011-04-15
0.3.2	0 / 2	2011-04-10
0.3.1	0 / 2	2011-02-19
0.3.0	0 / 2	2011-02-18
0.2.6	0 / 0	2011-02-21
0.2.5	0 / 0	2011-02-19
0.2.4	0 / 0	2011-02-03
0.2.3	0 / 0	2011-02-03
0.2.2	0 / 0	2011-02-03
0.2.1	0 / 0	2011-02-03
0.2.0	0 / 0	2011-02-03
0.1.3	0 / 0	2011-02-03
0.1.2	0 / 0	2011-02-03

v0.6.11

1 finding

LOW No provenance attestation provenance

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

v0.6.10

1 finding

LOW No provenance attestation provenance

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

v0.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

2 findings

HIGH Publisher changed: substack → ljharb (on 2022-10-13) provenance

This version was published by a different npm account than previous versions on 2022-10-13. 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.

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.