@atlaskit/teams-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/logo | AI (phantom-deps): Same-org scoped package in monorepo; phantom dep is expected pattern for workspace dependencies. | ai | |
| phantom-deps | phantom-dep:@atlaskit/icon-lab | AI (phantom-deps): Same-org scoped package in monorepo; phantom dep is expected pattern for workspace dependencies. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a well-known npm alias for react-intl@^5.18.1, a legitimate i18n library. Atlaskit packages routinely use this alias; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql-tag | AI (phantom-deps): Phantom dep referenced only in config files; common monorepo pattern for this Atlaskit package, not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same org scope phantom dep; common in Atlaskit monorepo packages where tokens are loaded by convention. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Phantom dep referenced only in config files; common monorepo pattern for this Atlaskit package, not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/string-hash | AI (phantom-deps): Framework-scoped type package loaded by convention; not a security concern for this Atlaskit package. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Phantom dep referenced only in config files; common monorepo pattern for this Atlaskit package, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher has 244 approved packages without provenance; this is a stable publishing pattern for this org, not a risk signal. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 32 / 14 | |
| 1.4.1 | 32 / 13 | |
| 1.4.0 | 32 / 13 | |
| 1.3.2 | 32 / 13 | |
| 1.3.1 | 32 / 13 | |
| 1.3.0 | 32 / 13 | |
| 1.2.0 | 32 / 13 | |
| 1.1.1 | 32 / 13 | |
| 1.1.0 | 32 / 12 | |
| 1.0.0 | 31 / 11 | |
| 0.74.2 | 32 / 10 | |
| 0.72.2 | 31 / 10 | |
| 0.72.1 | 32 / 10 | |
| 0.64.0 | 34 / 9 | |
| 0.63.3 | 36 / 9 | |
| 0.62.5 | 36 / 9 |
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.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.
v0.74.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.72.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.72.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.64.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.63.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.
v0.62.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.