@atlaskit/link-datasource
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 dep is same-org Atlassian package; consistent with established Atlaskit ecosystem patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Atlassian monorepo package; sparse README and no keywords are typical for internal component libraries published to npm. | ai | |
| phantom-deps | phantom-dep:@atlaskit/afm-i18n-platform-linking-platform-link-datasource | AI (phantom-deps): Same-org Atlassian i18n package; phantom dep finding is benign for this monorepo publishing pattern. | ai | |
| phantom-deps | phantom-dep:@types/dompurify | AI (phantom-deps): Type-only package loaded by convention; not a security concern. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 5.4.2 | 66 / 21 | |
| 5.4.1 | 66 / 19 | |
| 5.4.0 | 66 / 19 | |
| 5.3.0 | 65 / 19 | |
| 5.2.6 | 65 / 19 | |
| 5.2.5 | 65 / 19 | |
| 5.2.4 | 65 / 19 | |
| 5.2.3 | 65 / 19 | |
| 5.2.2 | 65 / 19 | |
| 5.2.1 | 65 / 18 | |
| 5.2.0 | 65 / 17 | |
| 5.1.0 | 65 / 17 | |
| 5.0.1 | 65 / 17 | |
| 5.0.0 | 65 / 17 | |
| 4.34.12 | 65 / 16 | |
| 4.34.11 | 65 / 16 | |
| 4.34.10 | 65 / 16 | |
| 4.34.9 | 65 / 16 | |
| 4.34.8 | 65 / 15 | |
| 4.34.7 | 65 / 15 | |
| 4.34.6 | 65 / 15 | |
| 4.34.5 | 65 / 15 | |
| 4.34.4 | 65 / 15 | |
| 4.34.3 | 65 / 15 | |
| 4.34.2 | 65 / 15 | |
| 4.34.1 | 65 / 15 | |
| 4.34.0 | 65 / 15 | |
| 4.33.12 | 65 / 15 | |
| 4.33.11 | 65 / 15 | |
| 4.33.10 | 65 / 15 | |
| 4.33.9 | 65 / 15 | |
| 4.33.8 | 65 / 15 | |
| 4.33.7 | 65 / 15 | |
| 4.33.6 | 65 / 15 | |
| 4.33.5 | 65 / 15 | |
| 4.33.4 | 65 / 15 | |
| 4.33.3 | 65 / 15 | |
| 4.33.2 | 65 / 15 | |
| 4.33.1 | 65 / 15 | |
| 4.33.0 | 65 / 15 | |
| 4.32.5 | 65 / 15 | |
| 4.32.4 | 65 / 15 | |
| 4.32.3 | 65 / 15 | |
| 4.32.2 | 65 / 14 | |
| 4.32.1 | 65 / 14 | |
| 4.32.0 | 65 / 14 | |
| 4.31.0 | 65 / 14 | |
| 4.30.18 | 65 / 15 | |
| 4.30.17 | 65 / 15 | |
| 4.30.16 | 65 / 15 | |
| 4.30.15 | 65 / 15 |
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.