← Home

jscs

npm Repository Homepage

JavaScript Code Style

92
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

hzoomarkelogmdevilsmikesherovmrjoelkempqfox

Keywords

code styleformatterlintlinterstyle guidevalidate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): hzoo (Henry Zhu) is explicitly listed as a named maintainer in package.json; the publisher change reflects a legitimate team transition, not a takeover. ai
phantom-deps phantom-dep:to-single-quotes AI (phantom-deps): to-single-quotes is a legitimate declared dependency used by jscs style rules. ai
bogus-package bogus-package AI (bogus-package): hzoo (Henry Zhu) is a well-known OSS contributor; flag is a false positive. jscs is a legitimate, long-established linter with 75k weekly downloads. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require(configPath) is intentional — jscs loads user config files by path, a core feature of any config-driven linter. Not a security risk. ai
phantom-deps phantom-dep:commander AI (phantom-deps): commander is a legitimate declared dependency used by the jscs CLI binary. ai
phantom-deps phantom-dep:to-double-quotes AI (phantom-deps): to-double-quotes is a legitimate declared dependency used by jscs style rules. ai

Versions (showing 92 of 92)

Version Deps Published
3.0.7 26 / 12
3.0.6 26 / 12
3.0.5 26 / 12
3.0.4 26 / 12
3.0.3 26 / 12
3.0.2 26 / 12
3.0.1 26 / 12
3.0.0 26 / 12
2.11.0 28 / 13
2.10.1 28 / 13
2.10.0 28 / 13
2.9.0 28 / 13
2.8.0 28 / 13
2.7.0 29 / 13
2.6.0 29 / 13
2.3.5 28 / 13
2.3.4 28 / 13
2.3.3 28 / 13
2.3.2 28 / 13
2.3.1 28 / 13
2.3.0 28 / 13
2.2.1 28 / 11
2.2.0 28 / 11
2.1.1 23 / 11
2.1.0 22 / 11
2.0.0 21 / 11
1.13.1 16 / 11
1.13.0 16 / 11
1.12.0 15 / 11
1.11.3 16 / 11
1.11.2 16 / 11
1.11.1 16 / 11
1.11.0 16 / 11
1.10.0 13 / 9
1.9.0 15 / 10
1.8.1 12 / 10
1.8.0 12 / 10
1.7.3 12 / 10
1.7.2 12 / 10
1.7.1 12 / 10
1.7.0 12 / 10
1.6.2 11 / 10
1.6.1 11 / 10
1.6.0 10 / 9
1.5.9 10 / 7
1.5.8 9 / 6
1.5.7 9 / 6
1.5.6 9 / 6
1.5.4 9 / 6
1.5.3 9 / 6
1.5.2 9 / 6
1.5.1 9 / 6
1.4.5 9 / 6
1.4.4 9 / 6
1.4.3 9 / 6
1.4.2 9 / 6
1.4.1 9 / 6
1.4.0 9 / 6
1.3.0 9 / 6
1.2.4 8 / 5
1.2.3 8 / 5
1.2.2 8 / 5
1.2.1 8 / 5
1.2.0 8 / 5
1.1.0 8 / 3
1.0.15 8 / 3
1.0.14 7 / 3
1.0.13 6 / 3
1.0.12 6 / 3
1.0.11 6 / 3
1.0.10 6 / 2
1.0.8 6 / 2
1.0.7 6 / 2
1.0.6 6 / 2
1.0.5 6 / 2
1.0.4 6 / 2
1.0.3 6 / 2
1.0.2 6 / 2
1.0.1 6 / 2
1.0.0 6 / 2
0.0.12 6 / 2
0.0.11 6 / 2
0.0.10 6 / 2
0.0.9 6 / 2
0.0.8 6 / 2
0.0.7 6 / 2
0.0.6 6 / 2
0.0.5 6 / 2
0.0.4 6 / 2
0.0.3 6 / 2
0.0.2 5 / 2
0.0.1 5 / 2

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

2 findings
HIGH Publisher changed: hzoo → markelog (on 2016-07-01) provenance

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

2 findings
HIGH Publisher changed: hzoo → markelog (on 2016-06-21) provenance

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

2 findings
HIGH Publisher changed: hzoo → markelog (on 2016-06-04) provenance

This version was published by a different npm account than previous versions on 2016-06-04. 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.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
HIGH Publisher changed: mdevils → hzoo (on 2016-04-15) provenance

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

v3.0.1

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

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.

v2.11.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-03-02) provenance

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

v2.10.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: hzoo → qfox (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.

v2.10.0

1 finding
LOW No provenance attestation provenance

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

v2.9.0

1 finding
LOW No provenance attestation provenance

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

v2.8.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-01-04) provenance

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

v2.7.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 2015-12-09) provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.3.5

1 finding
LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.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: markelog → hzoo (on 2015-09-28) provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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