← Home

cst

npm Repository Homepage

JavaScript CST Implementation

49
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

markeloghzoomdevils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): cst is a well-established Concrete Syntax Tree package, not a typosquat of jest. Edit distance of 2 is coincidental for a 3-letter acronym. ai
typosquat typosquat.levenshtein:got AI (typosquat): cst is a well-established Concrete Syntax Tree package, not a typosquat of got. Edit distance of 2 is coincidental for a 3-letter acronym. ai
typosquat typosquat.levenshtein:qs AI (typosquat): cst is a well-established Concrete Syntax Tree package, not a typosquat of qs. Edit distance of 2 is coincidental for a 3-letter acronym. ai
provenance publisher-changed AI (provenance): Publisher change hzoo→markelog occurred in 2017; both are listed co-maintainers in package.json. Long-established transition, not a current threat. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy coincides with the 2017 maintainer transition; package has 54 versions and continued activity since. Not indicative of takeover. ai
bogus-package bogus-package AI (bogus-package): hzoo spam flag is a false positive — Henry Zhu is a known Babel core contributor. No keywords is cosmetic. Package is legitimate. ai

Versions (showing 49 of 49)

Version Deps Published
0.4.10 3 / 20
0.4.9 3 / 20
0.4.8 3 / 20
0.4.7 3 / 14
0.4.6 3 / 14
0.4.5 3 / 14
0.4.4 3 / 14
0.4.3 3 / 14
0.4.2 3 / 14
0.4.1 2 / 13
0.4.0 4 / 14
0.3.0 4 / 14
0.2.0 4 / 14
0.1.6 4 / 14
0.1.5 4 / 14
0.1.4 4 / 14
0.1.3 4 / 14
0.1.2 3 / 14
0.1.1 3 / 14
0.0.30 2 / 10
0.0.29 2 / 10
0.0.28 2 / 10
0.0.27 2 / 10
0.0.26 2 / 10
0.0.25 2 / 10
0.0.24 1 / 10
0.0.23 1 / 10
0.0.22 1 / 10
0.0.21 1 / 10
0.0.20 1 / 10
0.0.19 1 / 10
0.0.18 1 / 10
0.0.17 1 / 10
0.0.16 1 / 10
0.0.15 1 / 9
0.0.14 1 / 9
0.0.13 1 / 9
0.0.12 1 / 10
0.0.11 1 / 10
0.0.10 1 / 10
0.0.9 1 / 10
0.0.8 1 / 10
0.0.7 1 / 10
0.0.6 1 / 10
0.0.5 1 / 10
0.0.4 1 / 10
0.0.3 1 / 9
0.0.2 1 / 9
0.0.1 0 / 2

v0.4.10

2 findings
HIGH Publisher changed: hzoo → markelog (on 2017-06-15) provenance

This version was published by a different npm account than previous versions on 2017-06-15. 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.4.9

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: markelog → hzoo (on 2016-11-15) provenance

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

v0.4.8

1 finding
LOW No provenance attestation provenance

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

v0.4.7

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

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: hzoo → markelog (on 2016-06-19) provenance

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

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

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: mdevils → hzoo (on 2016-05-17) provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

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: markelog → mdevils (on 2016-04-14) provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

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: mdevils → markelog (on 2016-03-17) provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

1 finding
LOW No provenance attestation provenance

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

v0.0.28

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: hzoo → mdevils (on 2016-02-18) provenance

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

v0.0.27

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: hzoo → mdevils (on 2016-02-18) provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

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: mdevils → hzoo (on 2016-02-15) provenance

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

v0.0.24

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: mdevils → hzoo (on 2016-01-30) provenance

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

v0.0.23

1 finding
LOW No provenance attestation provenance

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

v0.0.22

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

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: markelog → mdevils (on 2016-01-10) provenance

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

v0.0.17

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: markelog → mdevils (on 2016-01-09) provenance

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

v0.0.16

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: mdevils → markelog (on 2015-12-30) provenance

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

v0.0.15

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: hzoo → mdevils (on 2015-12-02) provenance

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

v0.0.14

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: mdevils → hzoo (on 2015-11-16) provenance

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

v0.0.13

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.0.6

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

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
LOW No provenance attestation provenance

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

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