@atlaskit/feature-gate-js-client
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@statsig/js-client | AI (dependencies): This package is explicitly a wrapper for the Statsig JS client; @statsig/js-client is a core, expected dependency. | ai | |
| dependencies | unvetted-dep:@statsig/client-core | AI (dependencies): Peer dependency of @statsig/js-client; expected and legitimate for this Statsig wrapper package. | ai | |
| dependencies | unvetted-dep:@atlaskit/atlassian-context | AI (dependencies): Same Atlassian monorepo package from the same publisher; entirely expected internal dependency. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes from a private monorepo; lack of Sigstore provenance is consistent across their packages and not a risk signal. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.7.1 | 5 / 2 | |
| 5.7.0 | 5 / 2 | |
| 5.6.0 | 5 / 2 | |
| 5.5.12 | 5 / 2 | |
| 5.5.11 | 5 / 2 | |
| 5.5.10 | 5 / 2 | |
| 5.5.9 | 5 / 2 | |
| 5.5.8 | 5 / 2 | |
| 5.5.7 | 5 / 2 | |
| 5.5.6 | 5 / 2 | |
| 5.5.5 | 5 / 2 | |
| 5.5.4 | 5 / 2 | |
| 5.5.3 | 5 / 3 | |
| 5.5.2 | 5 / 3 | |
| 5.5.1 | 5 / 3 | |
| 5.5.0 | 5 / 3 | |
| 5.4.0 | 5 / 3 | |
| 5.3.3 | 5 / 3 | |
| 5.3.2 | 5 / 3 | |
| 5.3.1 | 5 / 3 | |
| 5.3.0 | 5 / 3 |
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.