@atlaskit/inline-edit
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit scope phantom dep; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with strong track record; lack of Sigstore provenance is not a risk signal for this established publisher. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 15.6.16 | 13 / 17 | |
| 15.6.15 | 13 / 17 | |
| 15.6.14 | 13 / 17 | |
| 15.6.13 | 13 / 17 | |
| 15.6.12 | 13 / 16 | |
| 15.6.11 | 14 / 16 | |
| 15.6.10 | 14 / 16 | |
| 15.6.9 | 14 / 16 | |
| 15.6.8 | 14 / 15 | |
| 15.6.7 | 14 / 15 | |
| 15.6.6 | 14 / 15 | |
| 15.6.5 | 14 / 15 | |
| 15.6.4 | 14 / 15 | |
| 15.6.3 | 14 / 15 | |
| 15.6.2 | 14 / 15 | |
| 15.6.1 | 14 / 15 | |
| 15.6.0 | 14 / 15 | |
| 15.5.0 | 14 / 15 | |
| 15.4.2 | 14 / 15 | |
| 15.4.1 | 14 / 15 | |
| 15.4.0 | 14 / 15 | |
| 15.3.21 | 14 / 15 | |
| 15.3.20 | 14 / 15 | |
| 15.3.19 | 15 / 17 | |
| 15.3.18 | 15 / 17 | |
| 15.3.17 | 15 / 17 | |
| 15.3.16 | 15 / 17 | |
| 15.3.15 | 15 / 17 | |
| 15.3.14 | 15 / 17 | |
| 15.3.13 | 15 / 17 | |
| 15.3.12 | 15 / 17 | |
| 15.3.11 | 15 / 17 | |
| 15.3.10 | 15 / 17 | |
| 15.3.9 | 15 / 17 | |
| 15.3.8 | 15 / 17 | |
| 15.3.7 | 15 / 17 | |
| 15.3.6 | 15 / 17 | |
| 15.3.5 | 15 / 17 | |
| 15.3.4 | 15 / 18 | |
| 15.3.3 | 15 / 19 | |
| 15.3.2 | 15 / 19 | |
| 15.3.1 | 15 / 19 | |
| 15.3.0 | 15 / 19 | |
| 15.2.6 | 15 / 19 | |
| 15.2.5 | 15 / 19 | |
| 15.2.4 | 15 / 19 | |
| 15.2.3 | 15 / 19 | |
| 15.2.2 | 15 / 19 | |
| 15.2.1 | 15 / 19 | |
| 15.2.0 | 15 / 19 | |
| 15.1.5 | 15 / 19 |
v15.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.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.
v15.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.