@atlaskit/task-decision
Tasks and decisions react components
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org Atlassian phantom dep; consistent with Atlassian monorepo patterns. No security risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Atlassian package with 3200+ day history; lack of provenance attestation is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-next | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@atlaskit/util-service-support | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for this UI component package. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-namespaced-context | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@atlaskit/afm-i18n-platform-elements-task-decision | AI (dependencies): First-party @atlaskit scoped i18n dependency from the same Atlassian org. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org phantom dep in an Atlassian monorepo package; type-only or transitive usage is expected. | ai | |
| phantom-deps | phantom-dep:@atlaskit/afm-i18n-platform-elements-task-decision | AI (phantom-deps): Same-org phantom dep in an Atlassian monorepo package; indirect usage pattern is expected. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org. | ai | |
| dependencies | unvetted-dep:@compiled/react | AI (dependencies): Atlassian's own CSS-in-JS library; standard dependency across the @atlaskit ecosystem. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 20.1.13 | 11 / 17 | |
| 20.1.12 | 12 / 17 | |
| 20.1.11 | 12 / 17 | |
| 20.1.10 | 12 / 17 | |
| 20.1.9 | 12 / 17 | |
| 20.1.8 | 12 / 17 | |
| 20.1.7 | 12 / 17 | |
| 20.1.6 | 12 / 18 | |
| 20.1.5 | 12 / 18 | |
| 20.1.4 | 12 / 16 | |
| 20.1.3 | 12 / 16 | |
| 20.1.2 | 12 / 15 | |
| 20.1.1 | 12 / 15 | |
| 20.1.0 | 12 / 15 | |
| 20.0.18 | 12 / 15 | |
| 20.0.17 | 12 / 15 | |
| 20.0.16 | 12 / 15 | |
| 20.0.15 | 12 / 15 | |
| 20.0.14 | 12 / 15 | |
| 20.0.13 | 12 / 15 | |
| 20.0.12 | 12 / 15 | |
| 20.0.11 | 12 / 15 | |
| 20.0.10 | 12 / 15 | |
| 20.0.9 | 12 / 15 | |
| 20.0.8 | 12 / 15 | |
| 20.0.7 | 12 / 15 | |
| 20.0.6 | 12 / 15 | |
| 20.0.5 | 12 / 15 | |
| 20.0.4 | 12 / 15 | |
| 20.0.3 | 12 / 15 | |
| 20.0.2 | 12 / 15 | |
| 20.0.1 | 12 / 15 | |
| 20.0.0 | 12 / 15 | |
| 19.3.31 | 13 / 14 | |
| 19.3.30 | 13 / 14 | |
| 19.3.29 | 13 / 14 | |
| 19.3.28 | 13 / 14 | |
| 19.3.27 | 13 / 14 | |
| 19.3.25 | 13 / 14 | |
| 19.3.23 | 13 / 14 | |
| 19.3.20 | 13 / 14 | |
| 19.3.19 | 13 / 14 | |
| 19.3.17 | 13 / 14 | |
| 19.3.15 | 13 / 14 | |
| 19.3.14 | 13 / 14 | |
| 19.2.17 | 12 / 13 | |
| 19.2.15 | 12 / 13 | |
| 19.2.14 | 12 / 13 |
v20.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.