@atlaskit/jql-editor-autocomplete-rest
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Atlaskit monorepo packages routinely lack README code blocks and keywords; this is a structural pattern of Atlassian's internal component publishing, not a spam indicator. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 8 / 7 | |
| 3.2.0 | 8 / 7 | |
| 3.1.3 | 7 / 7 | |
| 3.1.2 | 7 / 6 | |
| 3.1.1 | 7 / 6 | |
| 3.1.0 | 7 / 7 | |
| 3.0.3 | 7 / 7 | |
| 3.0.2 | 7 / 5 | |
| 3.0.1 | 6 / 5 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.