@atlaskit/editor-plugin-placeholder-text
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/icon | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/adf-schema | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-analytics | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-type-ahead | AI (dependencies): First-party @atlaskit scoped dependency from the same Atlassian org; expected for an Atlaskit editor plugin. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit scoped package; phantom dep is a minor packaging artifact common in Atlassian monorepo builds, not a security concern. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 12.0.0 | 8 / 5 | |
| 11.1.1 | 8 / 3 | |
| 11.1.0 | 8 / 3 | |
| 11.0.0 | 8 / 3 | |
| 10.0.0 | 8 / 2 | |
| 9.0.31 | 8 / 2 | |
| 9.0.30 | 9 / 2 | |
| 9.0.29 | 9 / 2 | |
| 9.0.28 | 9 / 2 | |
| 9.0.27 | 9 / 2 | |
| 9.0.26 | 9 / 2 | |
| 9.0.25 | 9 / 2 | |
| 9.0.24 | 9 / 2 | |
| 9.0.23 | 9 / 2 | |
| 9.0.22 | 9 / 2 | |
| 9.0.21 | 9 / 2 | |
| 9.0.20 | 9 / 2 | |
| 9.0.19 | 9 / 2 | |
| 9.0.18 | 9 / 2 | |
| 9.0.17 | 9 / 2 | |
| 9.0.16 | 9 / 2 | |
| 9.0.15 | 9 / 2 | |
| 9.0.14 | 9 / 2 | |
| 9.0.13 | 9 / 2 | |
| 9.0.12 | 9 / 2 | |
| 9.0.11 | 9 / 2 | |
| 9.0.10 | 10 / 2 | |
| 9.0.9 | 10 / 2 | |
| 9.0.8 | 10 / 2 | |
| 9.0.7 | 10 / 2 | |
| 9.0.6 | 10 / 2 | |
| 9.0.5 | 10 / 2 | |
| 9.0.4 | 10 / 2 | |
| 9.0.3 | 10 / 2 | |
| 9.0.2 | 10 / 2 | |
| 9.0.1 | 10 / 2 | |
| 9.0.0 | 10 / 2 | |
| 8.0.26 | 10 / 2 | |
| 8.0.25 | 10 / 2 | |
| 8.0.24 | 10 / 2 | |
| 8.0.23 | 10 / 2 | |
| 8.0.22 | 10 / 2 | |
| 8.0.21 | 10 / 2 | |
| 8.0.20 | 10 / 2 | |
| 8.0.19 | 10 / 2 | |
| 8.0.18 | 10 / 2 | |
| 8.0.17 | 10 / 2 | |
| 8.0.16 | 10 / 2 | |
| 8.0.15 | 10 / 2 | |
| 8.0.14 | 10 / 2 | |
| 8.0.13 | 10 / 2 |
v12.0.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.29
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.