← Home

jsan

handle circular references when stringifying and parsing

22
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

kolodnyzalmoxisus

Keywords

json

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher kolodny is the package author and GitHub repo owner; transition from zalmoxisus is legitimate. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by publisher transition; original author resumed publishing a mature stable package. ai
bogus-package bogus-package AI (bogus-package): 35-byte index.js is a re-export pattern; short README is normal for a mature utility with 237k weekly downloads. ai

Versions (showing 22 of 22)

Version Deps Published
3.1.14 0 / 7
3.1.13 0 / 7
3.1.12 0 / 7
3.1.11 0 / 8
3.1.10 0 / 8
3.1.9 0 / 7
3.1.8 0 / 7
3.1.7 0 / 7
3.1.6 0 / 7
3.1.5 0 / 7
3.1.4 0 / 6
3.1.3 0 / 6
3.1.2 0 / 5
3.1.1 0 / 5
3.1.0 0 / 4
3.0.0 0 / 3
2.0.4 0 / 2
2.0.3 0 / 2
2.0.2 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2
1.0.0 0 / 2

v3.1.14

2 findings
HIGH Publisher changed: zalmoxisus → kolodny (on 2021-12-19) provenance

This version was published by a different npm account than previous versions on 2021-12-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.1.13

1 finding
LOW No provenance attestation provenance

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

v3.1.12

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kolodny → zalmoxisus (on 2018-12-01) provenance

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

v3.1.11

1 finding
LOW No provenance attestation provenance

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

v3.1.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: zalmoxisus → kolodny (on 2018-04-29) provenance

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

v3.1.9

1 finding
LOW No provenance attestation provenance

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

v3.1.8

1 finding
LOW No provenance attestation provenance

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

v3.1.7

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: kolodny → zalmoxisus (on 2017-02-18) provenance

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

v3.1.6

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.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.

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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