← Home

@atlaskit/teams-app-config

npm Repository Homepage
44
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@atlaskit/css AI (phantom-deps): Same-org scoped dependency in Atlassian Design System; phantom deps are expected in monorepo structures. ai
phantom-deps phantom-dep:@atlaskit/tokens AI (phantom-deps): Same-org scoped dependency in Atlassian Design System; phantom deps are expected in monorepo structures. ai
phantom-deps phantom-dep:@atlaskit/primitives AI (phantom-deps): Same-org scoped dependency in Atlassian Design System; phantom deps are expected in monorepo structures. ai
phantom-deps phantom-dep:@compiled/react AI (phantom-deps): Atlaskit packages routinely declare @compiled/react in config files for the Compiled CSS-in-JS build pipeline; the sideEffects field confirms this pattern. Not a real risk. ai

Versions (showing 44 of 44)

Version Deps Published
1.12.20 4 / 8
1.12.19 4 / 7
1.12.18 4 / 7
1.12.17 4 / 7
1.12.16 4 / 6
1.12.15 4 / 6
1.12.14 4 / 6
1.12.13 4 / 6
1.12.12 4 / 6
1.12.11 4 / 6
1.12.10 5 / 6
1.12.9 8 / 6
1.12.8 8 / 6
1.12.7 8 / 6
1.12.6 8 / 6
1.12.5 8 / 6
1.12.4 8 / 6
1.12.3 8 / 6
1.12.2 8 / 6
1.12.1 8 / 6
1.12.0 8 / 6
1.11.6 8 / 6
1.11.5 8 / 6
1.11.4 8 / 6
1.11.3 8 / 7
1.11.2 8 / 7
1.11.1 8 / 8
1.11.0 8 / 8
1.10.2 8 / 8
1.10.1 8 / 8
1.10.0 7 / 8
1.9.1 7 / 8
1.9.0 7 / 8
1.8.1 7 / 8
1.8.0 7 / 8
1.7.0 7 / 8
1.6.0 7 / 8
1.5.1 7 / 8
1.5.0 7 / 8
1.4.0 7 / 8
1.3.0 7 / 8
1.2.0 7 / 8
1.1.0 7 / 8
1.0.0 7 / 8

v1.12.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.