@atlaskit/people-teams-ui-public
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/legacy-custom-icons | AI (dependencies): Same-org @atlaskit scoped dependency; routine intra-org dependency within Atlassian's monorepo ecosystem, not a meaningful risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Same-org @atlaskit scoped phantom dep; common in Atlassian monorepo setups where packages are used transitively or in config. | ai | |
| phantom-deps | phantom-dep:@atlaskit/legacy-custom-icons | AI (phantom-deps): Same-org @atlaskit scoped phantom dep; common in Atlassian monorepo setups where packages are used transitively or in config. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is an npm alias for react-intl@^5.18.1, a well-known i18n library. This aliasing pattern is standard in the Atlaskit ecosystem and poses no security risk. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher consistently publishes without Sigstore provenance across their entire package portfolio; this is a stable characteristic of this publisher. | ai | |
| phantom-deps | phantom-dep:@compiled/react | AI (phantom-deps): @compiled/react is Atlaskit's standard CSS-in-JS build tooling; referenced in config files is expected behavior for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; consistent with this package's ecosystem. Not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit scoped package; phantom usage in config/build context is normal for Atlaskit packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit scoped package; phantom usage in config/build context is normal for Atlaskit packages. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/tooltip | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@atlaskit/analytics-namespaced-context | AI (dependencies): First-party Atlassian @atlaskit scoped dependency; consistent with this package's ecosystem. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 8 / 10 | |
| 4.0.3 | 8 / 10 | |
| 4.0.2 | 8 / 10 | |
| 4.0.1 | 8 / 10 | |
| 4.0.0 | 8 / 9 | |
| 3.7.14 | 9 / 8 | |
| 3.7.13 | 9 / 8 | |
| 3.7.12 | 9 / 8 | |
| 3.7.1 | 10 / 8 | |
| 3.6.2 | 12 / 8 | |
| 3.5.4 | 12 / 8 |
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.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.
v3.6.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.
v3.5.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.