@atlaskit/editor-plugin-ui-control-registry
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Atlassian routinely publishes AtlasKit monorepo packages at 0.0.0 as initial releases; this is a stable pattern for this publisher, not a malware indicator. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a build-time transpilation artifact injected by Babel; it is conventionally declared as a dependency in transpiled packages without direct imports in source. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlaskit monorepo packages routinely lack keywords and detailed READMEs; this is a cosmetic pattern, not a spam/malware signal for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 2 / 2 | |
| 4.1.0 | 2 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.0.0 | 2 / 1 | |
| 2.0.1 | 2 / 1 | |
| 2.0.0 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.0.0 | 1 / 1 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.