← Home

@atlaskit/jql-ast

npm Repository Homepage
4
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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:antlr4ts AI (dependencies): antlr4ts is the standard ANTLR4 TypeScript runtime; expected dependency for a JQL AST/parser package. ai
dependencies unvetted-dep:@atlaskit/jql-parser AI (dependencies): Sibling Atlaskit package for JQL parsing; expected dependency for this JQL AST package. ai
dependencies unvetted-dep:@atlaskit/platform-feature-flags AI (dependencies): Standard Atlaskit internal feature flags package; expected in Atlassian frontend monorepo packages. ai
bogus-package bogus-package AI (bogus-package): Internal Atlaskit monorepo package; sparse README and no keywords are typical for this ecosystem. ai

Versions (showing 4 of 4)

Version Deps Published
3.5.0 6 / 4
3.4.0 6 / 4
3.3.3 5 / 3
3.3.2 5 / 3

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.0

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.

v3.3.3

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.