@atlaskit/editor-smart-link-draggable
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party Atlaskit packages and react-intl (aliased as react-intl-next), all consistent with the package's drag-and-drop onboarding UI functionality. Publisher is well-established Atlassian team. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard npm alias (npm:react-intl@^5.x) used consistently across the entire Atlaskit package ecosystem; not a suspicious or malicious dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/primitives | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/smart-card | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/link-provider | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/linking-types | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/css | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/link-extractors | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes from a private Bitbucket monorepo; lack of Sigstore provenance is expected and consistent across all @atlaskit packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/linking-common | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Sibling @atlaskit package from the same Atlassian monorepo and publisher; unvetted status is a review pipeline artifact, not a security signal. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 13 / 1 | |
| 0.5.0 | 13 / 0 | |
| 0.4.3 | 13 / 0 | |
| 0.4.2 | 13 / 0 | |
| 0.4.1 | 13 / 0 | |
| 0.4.0 | 13 / 0 | |
| 0.3.1 | 16 / 0 | |
| 0.3.0 | 16 / 0 | |
| 0.2.1 | 16 / 0 | |
| 0.2.0 | 15 / 0 | |
| 0.1.4 | 12 / 0 | |
| 0.1.3 | 11 / 0 | |
| 0.1.2 | 11 / 0 | |
| 0.1.1 | 11 / 1 | |
| 0.1.0 | 5 / 2 |
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.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.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.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.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.