← Home

neotraverse

npm Repository Homepage

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

15
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

puruvj

Keywords

traversewalkrecursivemapforEachdeepclone

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:gopd AI (dependencies): gopd is a well-known Jordan Harband utility for own property descriptors; legitimate dependency for an object traversal library. ai
phantom-deps phantom-dep:klona AI (phantom-deps): klona is a legitimate deep-clone library declared in dependencies; its use in a traversal/transform package is expected and benign. ai
provenance no-provenance AI (provenance): Package predates widespread Sigstore provenance adoption; no other risk signals present. ai
source-diff obfuscated-file:dist/min/index.js AI (source-diff): Minified production build via terser/tsup; standard traverse library code visible in sample. Stable for this package. ai
source-diff obfuscated-file:dist/modern/min/modern.js AI (source-diff): Minified production build via terser/tsup; standard traverse library code visible in sample. Stable for this package. ai
provenance missing-githead AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor metadata gap, not a security concern. ai

Versions (showing 15 of 15)

Version Deps Published
0.6.18 0 / 7
0.6.17 0 / 7
0.6.16 0 / 7
0.6.15 0 / 6
0.6.14 0 / 6
0.6.13 0 / 6
0.6.12 0 / 6
0.6.11 0 / 6
0.6.10 0 / 6
0.6.9 0 / 6
0.6.8 0 / 6
0.0.5 0 / 6
0.0.3 0 / 6
0.0.2 0 / 5
0.0.1 4 / 5

v0.6.18

4 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: puruvj.

HIGH New obfuscated file: dist/min/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/modern/min/modern.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.6.17

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: puruvj.

v0.6.16

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: puruvj.

v0.6.15

1 finding
LOW No provenance attestation provenance

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

v0.6.14

1 finding
LOW No provenance attestation provenance

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

v0.6.13

1 finding
LOW No provenance attestation provenance

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

v0.6.12

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

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

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

v0.0.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.