← Home

@atlaskit/jql-parser

JQL lexer, parser, listener and visitor

4
Versions
Apache-2.0
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-lived Atlassian package with infrequent releases; dormancy is normal. ai
maintainer-change maintainer-takeover AI (maintainer-change): atlassianartifactteam is Atlassian's org-wide artifact publisher; transition from atlaskit is a known internal migration, not a hijack. ai
provenance publisher-changed AI (provenance): Publisher change reflects Atlassian's org-level migration to atlassianartifactteam; stable across all Atlaskit packages. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer is Atlassian's central artifact account; legitimate org migration. ai
maintainer-change maintainer-removed AI (maintainer-change): atlaskit removal is part of the same org migration; not a hostile takeover. ai
provenance missing-githead AI (provenance): Changed publish pipeline (org migration) explains missing gitHead; no other malicious indicators present. ai
dependencies unvetted-dep:antlr4ts AI (dependencies): antlr4ts is the standard ANTLR4 TypeScript runtime; its use is appropriate and expected for a JQL lexer/parser package. The alpha version is the de-facto stable release used widely. ai
bogus-package bogus-package AI (bogus-package): Atlassian internal/mirror packages commonly lack detailed READMEs and keywords; this is a cosmetic issue, not a spam/malware indicator. ai

Versions (showing 4 of 4)

Version Deps Published
3.0.0 2 / 1
2.1.0 2 / 1
2.0.1 2 / 3
2.0.0 2 / 3

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