@atlaskit/editor-plugin-scroll-into-view
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/link | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected internal dependency for Atlassian editor plugins. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected internal dependency for Atlassian editor plugins. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected internal dependency for Atlassian editor plugins. | ai | |
| dependencies | unvetted-dep:@atlaskit/prosemirror-input-rules | AI (dependencies): First-party Atlassian package in the same @atlaskit scope; expected internal dependency for Atlassian editor plugins. | ai | |
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same-org @atlaskit package; phantom dep pattern is common in Atlassian's monorepo build system. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit package; phantom dep pattern is common in Atlassian's monorepo build system. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard framework-level runtime dependency loaded by convention; not a real phantom dep concern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 5 / 4 | |
| 10.2.0 | 5 / 2 | |
| 10.1.0 | 5 / 2 | |
| 10.0.0 | 5 / 2 | |
| 9.0.0 | 5 / 2 | |
| 8.0.1 | 5 / 2 | |
| 8.0.0 | 5 / 2 | |
| 7.0.0 | 5 / 2 | |
| 6.0.2 | 5 / 2 | |
| 6.0.1 | 5 / 4 |
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.