← Home

@checkstack/integration-jira-backend

npm
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:Elastic-2.0 AI (license): Elastic-2.0 is a known license used consistently across this package family. ai
provenance no-provenance AI (provenance): Consistent pattern across this org's packages; no other risk indicators present. ai
dependencies unvetted-dep:@checkstack/automation-backend AI (dependencies): Same-org @checkstack scope; consistent with publisher's established package ecosystem. ai
dependencies unvetted-dep:@checkstack/integration-backend AI (dependencies): Same-org @checkstack scope; consistent with publisher's established package ecosystem. ai
provenance missing-githead AI (provenance): Established publisher with clean track record; missing gitHead alone is not a malware signal for this package. ai
npm-metadata no-description AI (npm-metadata): Internal monorepo package; missing description is expected and stable across versions. ai
phantom-deps phantom-dep:@checkstack/common AI (phantom-deps): Same org scope workspace dependency; phantom-dep false positive for monorepo packages. ai
bogus-package bogus-package AI (bogus-package): Monorepo workspace package; missing metadata is expected for internal packages, not a spam/malware indicator. ai
phantom-deps phantom-dep:@orpc/server AI (phantom-deps): Declared as a dependency; phantom-dep heuristic fires because it's referenced in config rather than directly imported — stable false positive for this package. ai
phantom-deps phantom-dep:@checkstack/integration-common AI (phantom-deps): Same-org scoped package; phantom-dep heuristic is a known false positive for org-internal shared libraries. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.1 8 / 5
0.1.13 7 / 4
0.1.12 7 / 4
0.1.9 7 / 4
0.1.8 7 / 4
0.1.3 7 / 4
0.0.18 7 / 4
0.0.14 7 / 4
0.0.10 7 / 4
0.0.8 7 / 4
0.0.3 7 / 4
0.0.2 7 / 4

v0.2.1

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

v0.1.13

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

v0.1.12

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

v0.1.9

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.

v0.1.8

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.

v0.1.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

LOW No provenance attestation provenance

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

v0.0.18

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

LOW No provenance attestation provenance

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

v0.0.14

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.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.