@atlaskit/profilecard
A React component to display a card with user information.
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
Keywords
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 @atlaskit/feature-gate-js-client, same Atlassian org scope; not a suspicious third-party addition. | ai | |
| dependencies | unvetted-dep:@atlassian/studio-entry-link | AI (dependencies): Same Atlassian org scope; consistent with this package's established dependency pattern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/logo | AI (phantom-deps): Monorepo package; phantom deps in same org scope are typical of hoisted workspace dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Monorepo package; phantom deps in same org scope are typical of hoisted workspace dependencies. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Monorepo package; phantom deps referenced in config files are typical of hoisted workspace dependencies. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Monorepo package; phantom deps referenced in config files are typical of hoisted workspace dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/feature-gate-js-client | AI (phantom-deps): Monorepo package; phantom deps in same org scope are typical of hoisted workspace dependencies. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a version alias for the well-known react-intl library; its use in Atlassian UI components is expected and benign. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org phantom dep flag for @atlaskit/tokens; consistent with Atlaskit monorepo build patterns, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire @atlaskit/* ecosystem without Sigstore provenance; this is consistent across all their packages and not a security concern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash phantom dep is a common false positive in monorepo/build-tool setups; no security concern for this established Atlaskit package. | ai |
Versions (showing 86 of 86)
| Version | Deps | Published |
|---|---|---|
| 25.8.0 | 41 / 21 | |
| 25.7.10 | 40 / 22 | |
| 25.7.8 | 40 / 22 | |
| 25.7.6 | 40 / 22 | |
| 25.7.3 | 40 / 22 | |
| 25.7.1 | 40 / 20 | |
| 25.7.0 | 40 / 20 | |
| 25.6.3 | 40 / 20 | |
| 25.6.2 | 40 / 20 | |
| 25.6.1 | 40 / 20 | |
| 25.6.0 | 40 / 20 | |
| 25.5.2 | 40 / 20 | |
| 25.5.1 | 40 / 20 | |
| 25.5.0 | 40 / 20 | |
| 25.4.4 | 40 / 20 | |
| 25.4.3 | 40 / 20 | |
| 25.4.2 | 40 / 20 | |
| 25.4.1 | 40 / 20 | |
| 25.3.0 | 40 / 20 | |
| 25.2.1 | 39 / 20 | |
| 25.2.0 | 39 / 20 | |
| 25.1.16 | 39 / 20 | |
| 25.1.15 | 39 / 20 | |
| 25.1.14 | 39 / 20 | |
| 25.1.13 | 39 / 20 | |
| 25.1.12 | 39 / 20 | |
| 25.1.11 | 39 / 20 | |
| 25.1.10 | 39 / 20 | |
| 25.1.9 | 39 / 20 | |
| 25.1.8 | 39 / 20 | |
| 25.1.7 | 39 / 20 | |
| 25.1.6 | 39 / 20 | |
| 25.1.5 | 39 / 20 | |
| 25.1.4 | 39 / 20 | |
| 25.1.3 | 39 / 20 | |
| 25.1.2 | 39 / 20 | |
| 25.1.1 | 39 / 20 | |
| 25.1.0 | 39 / 20 | |
| 25.0.3 | 39 / 20 | |
| 25.0.2 | 39 / 19 | |
| 25.0.1 | 39 / 19 | |
| 25.0.0 | 39 / 19 | |
| 24.49.10 | 40 / 18 | |
| 24.49.9 | 40 / 18 | |
| 24.49.7 | 40 / 18 | |
| 24.49.4 | 40 / 18 | |
| 24.49.1 | 40 / 18 | |
| 24.49.0 | 40 / 18 | |
| 24.48.3 | 40 / 19 | |
| 24.48.2 | 40 / 19 | |
| 24.48.1 | 40 / 19 | |
| 24.48.0 | 40 / 19 | |
| 24.46.4 | 39 / 19 | |
| 24.46.3 | 39 / 19 | |
| 24.46.1 | 39 / 19 | |
| 24.45.3 | 39 / 19 | |
| 24.45.2 | 39 / 19 | |
| 24.45.1 | 39 / 19 | |
| 24.44.16 | 39 / 19 | |
| 24.44.15 | 39 / 19 | |
| 24.44.14 | 39 / 19 | |
| 24.44.13 | 39 / 19 | |
| 24.44.12 | 39 / 19 | |
| 24.44.10 | 39 / 19 | |
| 24.44.2 | 39 / 19 | |
| 24.44.1 | 39 / 19 | |
| 24.40.2 | 41 / 19 | |
| 24.40.0 | 41 / 19 | |
| 24.38.0 | 40 / 19 | |
| 24.37.3 | 40 / 19 | |
| 24.34.5 | 41 / 18 | |
| 24.34.4 | 41 / 18 | |
| 24.34.2 | 41 / 18 | |
| 24.32.3 | 40 / 18 | |
| 24.32.2 | 40 / 17 | |
| 24.30.2 | 40 / 13 | |
| 24.29.1 | 40 / 14 | |
| 24.27.2 | 40 / 14 | |
| 24.27.1 | 40 / 14 | |
| 24.24.2 | 40 / 14 | |
| 24.21.8 | 42 / 14 | |
| 24.21.6 | 42 / 14 | |
| 24.21.4 | 42 / 14 | |
| 24.21.3 | 42 / 14 | |
| 24.21.1 | 42 / 14 | |
| 24.20.4 | 44 / 14 |
v25.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.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.
v24.49.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.
v24.49.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.
v24.49.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.
v24.49.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.
v24.49.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.
v24.49.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.
v24.48.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.
v24.48.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.
v24.48.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.
v24.48.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.
v24.46.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.
v24.46.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.
v24.46.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.
v24.45.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.
v24.45.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.
v24.45.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.44.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.
v24.40.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.
v24.40.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.
v24.38.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.
v24.37.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.
v24.34.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.
v24.34.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.
v24.34.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.
v24.32.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.
v24.32.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.
v24.30.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.
v24.29.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.
v24.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.
v24.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.
v24.24.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.
v24.21.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.
v24.21.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.
v24.21.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.
v24.21.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.
v24.21.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.
v24.20.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.