@atlaskit/node-data-provider
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:@atlaskit/editor-prosemirror | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected dependency for an Atlaskit editor component. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected dependency for an Atlaskit editor component. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected dependency for an Atlaskit editor component. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-json-transformer | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected dependency for an Atlaskit editor component. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same org scope (@atlaskit); declared but not directly imported is a minor packaging concern, not a security risk. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 12.0.1 | 5 / 0 | |
| 12.0.0 | 5 / 0 | |
| 11.1.7 | 5 / 0 | |
| 11.1.6 | 5 / 0 | |
| 11.1.5 | 5 / 0 | |
| 11.1.4 | 5 / 0 | |
| 11.1.3 | 5 / 0 | |
| 11.1.2 | 5 / 0 | |
| 11.1.1 | 5 / 0 | |
| 11.1.0 | 5 / 0 | |
| 11.0.18 | 5 / 0 | |
| 11.0.17 | 5 / 0 | |
| 11.0.16 | 5 / 0 | |
| 11.0.15 | 5 / 0 | |
| 11.0.14 | 5 / 0 | |
| 11.0.13 | 5 / 0 | |
| 11.0.12 | 5 / 0 | |
| 11.0.11 | 5 / 0 | |
| 11.0.10 | 5 / 0 | |
| 11.0.9 | 5 / 0 | |
| 11.0.8 | 5 / 0 | |
| 11.0.7 | 5 / 0 | |
| 11.0.6 | 5 / 0 | |
| 11.0.5 | 5 / 0 | |
| 11.0.4 | 5 / 0 | |
| 11.0.3 | 5 / 0 | |
| 11.0.2 | 5 / 0 | |
| 11.0.1 | 5 / 0 | |
| 11.0.0 | 5 / 0 | |
| 10.0.0 | 5 / 0 | |
| 9.0.28 | 5 / 0 | |
| 9.0.27 | 5 / 0 | |
| 9.0.26 | 5 / 0 | |
| 9.0.25 | 5 / 0 | |
| 9.0.24 | 5 / 0 | |
| 9.0.23 | 5 / 0 | |
| 9.0.22 | 5 / 0 | |
| 9.0.21 | 5 / 0 | |
| 9.0.20 | 5 / 0 | |
| 9.0.19 | 5 / 0 | |
| 9.0.18 | 5 / 0 | |
| 9.0.17 | 5 / 0 | |
| 9.0.16 | 5 / 0 | |
| 9.0.15 | 5 / 0 | |
| 9.0.14 | 5 / 0 | |
| 9.0.13 | 5 / 0 | |
| 9.0.12 | 5 / 0 | |
| 9.0.11 | 5 / 0 | |
| 9.0.10 | 5 / 0 | |
| 9.0.9 | 5 / 0 | |
| 9.0.8 | 5 / 0 | |
| 9.0.7 | 5 / 0 | |
| 9.0.6 | 5 / 0 | |
| 9.0.5 | 5 / 0 | |
| 9.0.4 | 5 / 0 | |
| 9.0.3 | 5 / 0 | |
| 9.0.2 | 5 / 0 | |
| 9.0.1 | 5 / 0 | |
| 9.0.0 | 5 / 0 | |
| 8.3.12 | 5 / 0 | |
| 8.3.11 | 5 / 0 | |
| 8.3.10 | 5 / 0 | |
| 8.3.9 | 5 / 0 | |
| 8.3.8 | 5 / 0 | |
| 8.3.7 | 5 / 0 | |
| 8.3.6 | 5 / 0 | |
| 8.3.5 | 5 / 0 | |
| 8.3.4 | 5 / 0 | |
| 8.3.3 | 5 / 0 | |
| 8.3.2 | 5 / 0 | |
| 8.3.1 | 5 / 0 | |
| 8.3.0 | 4 / 0 | |
| 8.2.0 | 4 / 0 | |
| 8.1.0 | 4 / 0 | |
| 8.0.0 | 3 / 0 | |
| 7.5.2 | 4 / 0 | |
| 7.5.1 | 5 / 0 | |
| 7.5.0 | 5 / 0 | |
| 7.4.0 | 5 / 0 | |
| 7.3.0 | 5 / 0 |
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.