@atlaskit/smart-card
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:@atlaskit/motion | AI (phantom-deps): Same @atlaskit org scope; phantom-dep pattern is consistent with this package's peer/optional dependency structure. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon-priority | AI (dependencies): Internal @atlaskit org dependency published by the same Atlassian team; not a third-party risk. Stable pattern for this monorepo package. | ai | |
| dependencies | unvetted-dep:@atlaskit/legacy-custom-icons | AI (dependencies): Internal @atlaskit org dependency published by the same Atlassian team; not a third-party risk. Stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/icon-lab | AI (phantom-deps): Same-org @atlaskit scope phantom dep; typical of large Atlassian monorepo packages where deps are declared for tooling but not directly imported. | ai | |
| phantom-deps | phantom-dep:@atlaskit/icon-priority | AI (phantom-deps): Same-org @atlaskit scope phantom dep; typical of large Atlassian monorepo packages where deps are declared for tooling but not directly imported. | ai | |
| phantom-deps | phantom-dep:@atlaskit/icon-file-type | AI (phantom-deps): Same-org @atlaskit/* monorepo peer/dev deps declared but not directly imported in every file — expected pattern for Atlaskit packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/link-test-helpers | AI (phantom-deps): Same-org @atlaskit/* monorepo peer/dev deps declared but not directly imported in every file — expected pattern for Atlaskit packages. | ai | |
| phantom-deps | phantom-dep:facepaint | AI (phantom-deps): Referenced in config files only (e.g. emotion/styled config), not directly imported — common pattern in Atlaskit design system packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/afm-i18n-platform-linking-platform-smart-card | AI (phantom-deps): Same-org @atlaskit/* monorepo peer/dev deps declared but not directly imported in every file — expected pattern for Atlaskit packages. | ai | |
| source-diff | obfuscated-file:dist/cjs/view/HoverCard/components/views/unauthorised/graphics.js | AI (source-diff): Long lines are SVG path coordinate data in @compiled/babel-plugin generated output — not obfuscation. Stable false positive for this Atlaskit package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/es2019/view/HoverCard/components/views/unauthorised/graphics.js | AI (source-diff): Long lines are SVG path coordinate data in @compiled/babel-plugin generated output — not obfuscation. Stable false positive for this Atlaskit package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/esm/view/HoverCard/components/views/unauthorised/graphics.js | AI (source-diff): Long lines are SVG path coordinate data in @compiled/babel-plugin generated output — not obfuscation. Stable false positive for this Atlaskit package's build pipeline. | ai | |
| phantom-deps | phantom-dep:@atlaskit/avatar | AI (phantom-deps): Same-org @atlaskit/* monorepo peer/dev deps declared but not directly imported in every file — expected pattern for Atlaskit packages. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes all @atlaskit/* packages without Sigstore provenance; this is a stable pattern for this publisher and not a security concern. | ai |
Versions (showing 67 of 176)
| Version | Deps | Published |
|---|---|---|
| 44.0.4 | 66 / 37 | |
| 44.0.3 | 66 / 37 | |
| 44.0.2 | 66 / 37 | |
| 44.0.1 | 66 / 37 | |
| 44.0.0 | 66 / 37 | |
| 43.32.0 | 66 / 37 | |
| 43.31.10 | 66 / 37 | |
| 43.31.9 | 66 / 37 | |
| 43.31.8 | 66 / 37 | |
| 43.31.7 | 66 / 37 | |
| 43.31.6 | 67 / 37 | |
| 43.31.5 | 67 / 37 | |
| 43.31.4 | 67 / 37 | |
| 43.31.3 | 67 / 37 | |
| 43.31.2 | 67 / 36 | |
| 43.31.1 | 67 / 36 | |
| 43.31.0 | 67 / 36 | |
| 43.30.1 | 67 / 36 | |
| 43.30.0 | 66 / 36 | |
| 43.29.3 | 66 / 36 | |
| 43.29.2 | 66 / 36 | |
| 43.29.1 | 66 / 36 | |
| 43.29.0 | 66 / 36 | |
| 43.28.7 | 65 / 36 | |
| 43.28.6 | 65 / 36 | |
| 43.28.5 | 65 / 36 | |
| 43.28.4 | 65 / 36 | |
| 43.28.2 | 65 / 36 | |
| 43.28.1 | 65 / 36 | |
| 43.28.0 | 65 / 36 | |
| 43.27.5 | 65 / 36 | |
| 43.27.4 | 65 / 36 | |
| 43.27.3 | 65 / 36 | |
| 43.27.2 | 65 / 36 | |
| 43.27.1 | 64 / 36 | |
| 43.27.0 | 64 / 36 | |
| 43.26.13 | 64 / 36 | |
| 43.26.12 | 64 / 36 | |
| 43.26.11 | 64 / 36 | |
| 43.26.10 | 64 / 36 | |
| 43.26.9 | 64 / 36 | |
| 43.26.8 | 64 / 36 | |
| 43.26.7 | 64 / 36 | |
| 43.26.6 | 64 / 36 | |
| 43.26.5 | 64 / 36 | |
| 43.26.4 | 64 / 36 | |
| 43.26.3 | 63 / 36 | |
| 43.26.2 | 63 / 36 | |
| 43.26.1 | 63 / 36 | |
| 43.26.0 | 63 / 36 | |
| 43.25.16 | 63 / 36 | |
| 43.25.15 | 63 / 36 | |
| 43.25.14 | 62 / 36 | |
| 43.25.13 | 62 / 36 | |
| 43.25.12 | 62 / 36 | |
| 43.25.11 | 62 / 36 | |
| 43.25.10 | 62 / 36 | |
| 43.25.6 | 63 / 36 | |
| 43.25.0 | 63 / 36 | |
| 43.23.6 | 62 / 36 | |
| 43.22.5 | 62 / 36 | |
| 43.22.0 | 62 / 36 | |
| 43.20.6 | 62 / 36 | |
| 43.16.0 | 62 / 37 | |
| 43.15.1 | 62 / 37 | |
| 43.14.1 | 62 / 37 | |
| 43.3.1 | 61 / 36 |
v44.0.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.0.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.0.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.0.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.0.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.32.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.10
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.9
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.8
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.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.
v43.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.31.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.
v43.30.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.
v43.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.29.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.
v43.29.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.
v43.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v43.29.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.
v43.28.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.28.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.
v43.28.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.
v43.28.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.
v43.28.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.
v43.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.27.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.
v43.27.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.
v43.27.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.
v43.27.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.
v43.27.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.
v43.26.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.26.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.
v43.26.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.
v43.26.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.
v43.26.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.
v43.26.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.
v43.25.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.25.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.
v43.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.22.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.
v43.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v43.16.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.
v43.15.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.
v43.14.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.
v43.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.