jira-client
1
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
mtscout6kanoyugoropiouggeddyseth10001
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:postman-request | AI (dependencies): Known request fork maintained by Postman; standard dep for JIRA API wrappers. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 8.2.2 | 2 / 19 |
v8.2.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.