← Home

jscs-jsdoc

npm Repository Homepage

JSCS jsdoc plugin

42
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

mdevilsqfox

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from qfox to mdevils is a documented legitimate transition within the jscs-dev org. mdevils has a 96/0 approval record and is the canonical jscs ecosystem maintainer. ai
maintainer-change maintainer-added AI (maintainer-change): mdevils added as maintainer is consistent with the jscs-dev org ownership. Long-standing trusted publisher with clean track record. ai

Versions (showing 42 of 42)

Version Deps Published
2.0.0 2 / 5
1.3.2 2 / 5
1.3.1 2 / 5
1.3.0 2 / 5
1.2.0 2 / 5
1.1.0 2 / 4
1.0.1 2 / 4
1.0.0 2 / 4
0.4.6 2 / 4
0.4.5 2 / 4
0.4.4 2 / 4
0.4.3 2 / 4
0.4.2 2 / 4
0.4.1 2 / 4
0.4.0 2 / 4
0.3.2 2 / 4
0.3.1 2 / 4
0.3.0 3 / 4
0.2.0 2 / 6
0.1.1 2 / 6
0.1.0 2 / 6
0.0.24 2 / 6
0.0.23 2 / 6
0.0.22 2 / 6
0.0.21 2 / 6
0.0.20 2 / 6
0.0.18 2 / 6
0.0.17 2 / 6
0.0.16 2 / 6
0.0.15 2 / 6
0.0.14 2 / 6
0.0.13 2 / 6
0.0.12 2 / 6
0.0.11 2 / 6
0.0.10 2 / 6
0.0.9 2 / 6
0.0.6 1 / 4
0.0.5 1 / 4
0.0.4 1 / 4
0.0.3 1 / 4
0.0.2 1 / 4
0.0.1 1 / 4

v2.0.0

2 findings
HIGH Publisher changed: qfox → mdevils (on 2016-04-14) provenance

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.

LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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