jsdoc-type-pratt-parser
[](https://www.npmjs.com/package/jsdoc-type-pratt-parser) []
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA provenance attestation; consistent with semantic-release adoption by the original author. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): simonseyock2 is the original author's account; brettz9 is a listed contributor. Both are known JSDoc ecosystem maintainers. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed account was an org/bot account replaced by personal accounts of known maintainers; legitimate transition. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 37 | |
| 7.1.1 | 0 / 38 | |
| 7.1.0 | 0 / 38 | |
| 7.0.0 | 0 / 38 | |
| 6.11.1 | 0 / 38 | |
| 6.11.0 | 0 / 37 | |
| 6.10.0 | 0 / 37 | |
| 6.9.1 | 0 / 37 | |
| 6.9.0 | 0 / 37 | |
| 6.8.0 | 0 / 37 | |
| 6.7.0 | 0 / 37 | |
| 6.6.0 | 0 / 37 | |
| 6.5.1 | 0 / 37 | |
| 6.5.0 | 0 / 37 | |
| 6.4.0 | 0 / 37 | |
| 6.3.3 | 0 / 37 | |
| 6.3.2 | 0 / 37 | |
| 6.3.1 | 0 / 37 | |
| 6.3.0 | 0 / 37 | |
| 6.2.0 | 0 / 37 | |
| 6.1.2 | 0 / 37 | |
| 6.1.1 | 0 / 37 | |
| 6.1.0 | 0 / 37 | |
| 6.0.1 | 0 / 37 | |
| 6.0.0 | 0 / 37 | |
| 5.9.2 | 0 / 37 | |
| 5.9.1 | 0 / 37 | |
| 5.9.0 | 0 / 37 | |
| 5.8.0 | 0 / 33 | |
| 5.7.0 | 0 / 33 | |
| 5.6.0 | 0 / 33 | |
| 5.5.0 | 0 / 33 | |
| 5.4.0 | 0 / 33 | |
| 5.3.0 | 0 / 33 | |
| 5.2.0 | 0 / 33 | |
| 5.1.1 | 0 / 33 | |
| 5.1.0 | 0 / 33 | |
| 5.0.0 | 0 / 33 | |
| 4.8.0 | 0 / 26 | |
| 4.7.0 | 0 / 26 | |
| 4.6.0 | 0 / 26 | |
| 4.5.0 | 0 / 26 | |
| 4.4.1 | 0 / 26 | |
| 4.4.0 | 0 / 26 | |
| 4.3.0 | 0 / 26 | |
| 4.2.0 | 0 / 26 | |
| 4.1.0 | 0 / 26 | |
| 4.0.0 | 0 / 26 | |
| 3.1.0 | 0 / 26 | |
| 3.0.1 | 0 / 26 | |
| 3.0.0 | 0 / 26 | |
| 2.2.5 | 0 / 26 | |
| 2.2.4 | 0 / 26 | |
| 2.2.3 | 0 / 26 | |
| 2.2.2 | 0 / 26 | |
| 2.2.1 | 0 / 25 | |
| 2.2.0 | 0 / 25 | |
| 2.1.0 | 0 / 25 | |
| 2.0.2 | 0 / 24 | |
| 2.0.1 | 0 / 24 | |
| 2.0.0 | 0 / 24 | |
| 1.2.0 | 0 / 22 | |
| 1.1.1 | 0 / 22 | |
| 1.0.8 | 0 / 21 | |
| 1.0.7 | 0 / 21 | |
| 1.0.6 | 0 / 21 | |
| 1.0.4 | 0 / 21 | |
| 1.0.3 | 0 / 21 | |
| 1.0.2 | 0 / 21 | |
| 1.0.1 | 0 / 19 | |
| 1.0.0 | 0 / 19 |
v7.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.