@squidcloud/jira-jsm-client
Squid Jira Service Management Client - SDK for interacting with the JSM connector
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): squid.cloud is the org account for the squidcloud ecosystem with 7 approved packages; transition from personal to org account is expected. | ai | |
| phantom-deps | phantom-dep:assertic | AI (phantom-deps): assertic is a declared dependency used via config/indirect import; stable false positive for this package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.0.482 | 2 / 0 | |
| 1.0.481 | 2 / 0 | |
| 1.0.479 | 2 / 0 | |
| 1.0.478 | 2 / 0 | |
| 1.0.477 | 2 / 0 | |
| 1.0.476 | 2 / 0 | |
| 1.0.475 | 2 / 0 | |
| 1.0.474 | 2 / 0 | |
| 1.0.473 | 2 / 0 | |
| 1.0.472 | 2 / 0 | |
| 1.0.471 | 2 / 0 | |
| 1.0.470 | 2 / 0 | |
| 1.0.469 | 2 / 0 | |
| 1.0.468 | 2 / 0 | |
| 1.0.467 | 2 / 0 | |
| 1.0.466 | 2 / 0 | |
| 1.0.465 | 2 / 0 | |
| 1.0.464 | 2 / 0 | |
| 1.0.463 | 2 / 0 | |
| 1.0.462 | 2 / 0 | |
| 1.0.461 | 2 / 0 | |
| 1.0.460 | 2 / 0 | |
| 1.0.459 | 2 / 0 | |
| 1.0.458 | 2 / 0 | |
| 1.0.457 | 2 / 0 | |
| 1.0.456 | 2 / 0 | |
| 1.0.455 | 2 / 0 | |
| 1.0.454 | 2 / 0 | |
| 1.0.453 | 2 / 0 | |
| 1.0.452 | 2 / 0 | |
| 1.0.451 | 2 / 0 | |
| 1.0.450 | 2 / 0 | |
| 1.0.449 | 2 / 0 | |
| 1.0.447 | 2 / 0 | |
| 1.0.446 | 2 / 0 | |
| 1.0.445 | 2 / 0 | |
| 1.0.444 | 2 / 0 | |
| 1.0.443 | 2 / 0 | |
| 1.0.442 | 2 / 0 | |
| 1.0.441 | 2 / 0 | |
| 1.0.440 | 2 / 0 | |
| 1.0.439 | 2 / 0 | |
| 1.0.438 | 2 / 0 | |
| 1.0.436 | 2 / 0 | |
| 1.0.435 | 2 / 0 | |
| 1.0.434 | 2 / 0 | |
| 1.0.433 | 2 / 0 |
v1.0.482
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mfursov) than the most recent previously approved version (robbert_squid) on 2026-07-17, but mfursov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.481
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (robbert_squid) than the most recent previously approved version (wynnch-squid-ai) on 2026-07-15, but robbert_squid is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.479
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wynnch-squid-ai) than the most recent previously approved version (mfursov) on 2026-07-13, but wynnch-squid-ai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.478
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mfursov) than the most recent previously approved version (squid.cloud) on 2026-07-12, but mfursov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.477
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.476
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.475
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.474
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (squid.cloud) than the most recent previously approved version (victor-at-squid) on 2026-06-30, but squid.cloud is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.