@atlaskit/teams-client
A client to retrieve team related data
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 | dormant-publish | AI (publish-pattern): Atlassian publisher with strong track record; infrequent release cadence is plausible for an internal SDK package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/feature-gate-js-client | AI (phantom-deps): Same-org scope; typical monorepo transitive dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:faker | AI (dependencies): faker is a phantom/dev-only dependency used for test data generation in config files, not imported at runtime. Stable false positive for this Atlassian package. | ai | |
| phantom-deps | phantom-dep:faker | AI (phantom-deps): faker is referenced only in config files (likely test data generation), not imported at runtime. This is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher consistently publishes without Sigstore provenance across 255+ approved packages; this is a stable pattern for this publisher. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 4.33.0 | 10 / 11 | |
| 4.32.5 | 10 / 11 | |
| 4.32.4 | 10 / 11 | |
| 4.32.3 | 10 / 11 | |
| 4.32.1 | 10 / 10 | |
| 4.32.0 | 10 / 10 | |
| 4.31.0 | 10 / 10 | |
| 4.30.3 | 10 / 10 | |
| 4.30.2 | 10 / 10 | |
| 4.30.1 | 11 / 10 | |
| 4.28.0 | 11 / 10 | |
| 4.27.0 | 11 / 10 | |
| 4.26.0 | 11 / 10 | |
| 4.24.0 | 11 / 10 | |
| 4.23.0 | 11 / 10 | |
| 4.22.0 | 11 / 10 | |
| 4.19.0 | 11 / 10 | |
| 4.18.0 | 11 / 10 | |
| 4.17.0 | 11 / 10 | |
| 4.15.1 | 11 / 10 | |
| 4.15.0 | 11 / 10 | |
| 4.14.0 | 11 / 10 | |
| 4.13.1 | 11 / 10 | |
| 4.12.0 | 11 / 10 | |
| 4.10.0 | 11 / 11 | |
| 4.8.2 | 11 / 10 | |
| 4.8.1 | 11 / 10 | |
| 4.6.2 | 11 / 10 | |
| 4.6.0 | 11 / 10 | |
| 4.5.1 | 11 / 10 | |
| 4.5.0 | 11 / 10 | |
| 4.3.0 | 11 / 10 | |
| 4.2.0 | 11 / 10 | |
| 4.1.0 | 11 / 10 | |
| 4.0.0 | 11 / 10 |
v4.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.32.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.
v4.32.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.
v4.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.
v4.30.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.24.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.
v4.23.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.
v4.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.
v4.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.