@atlaskit/editor-plugin-border
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:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard transitive runtime dep loaded by convention in the Atlaskit build pipeline; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire Atlaskit ecosystem without Sigstore provenance; this is a stable characteristic of the publisher, not a risk signal. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 2 / 4 | |
| 10.1.0 | 2 / 2 | |
| 10.0.0 | 2 / 2 | |
| 9.0.0 | 2 / 2 | |
| 8.0.1 | 2 / 2 | |
| 8.0.0 | 2 / 2 | |
| 7.0.1 | 2 / 2 | |
| 7.0.0 | 2 / 2 | |
| 6.1.4 | 2 / 2 | |
| 6.1.3 | 2 / 4 |
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.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.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.