@atlaskit/jql-ast
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo publish metadata gap, no behavioral signal, trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): Provenance unchanged vs prior approved; not a regression. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Provenance confirms known-maintainer manual publish, not a hijack; stable across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is email-matched known contributor per provenance data. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same benign account transition, not a takeover. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Standard Atlaskit internal feature flags package; expected in Atlassian frontend monorepo packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/jql-parser | AI (dependencies): Sibling Atlaskit package for JQL parsing; expected dependency for this JQL AST package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Atlaskit monorepo package; sparse README and no keywords are typical for this ecosystem. | ai | |
| dependencies | unvetted-dep:antlr4ts | AI (dependencies): antlr4ts is the standard ANTLR4 TypeScript runtime; expected dependency for a JQL AST/parser package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 6 / 4 | |
| 3.5.0 | 6 / 4 | |
| 3.4.0 | 6 / 4 | |
| 3.3.3 | 5 / 3 | |
| 3.3.2 | 5 / 3 | |
| 3.3.1 | 5 / 4 | |
| 3.3.0 | 5 / 4 | |
| 3.2.0 | 5 / 5 | |
| 3.1.1 | 5 / 5 | |
| 3.1.0 | 5 / 5 | |
| 3.0.0 | 5 / 5 |
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
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 (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-07, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.