@atlaskit/give-kudos
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-peer-dep:react-intl-next | AI (dependencies): Peer dependency alias for react-intl; expected for i18n library integration in consumer apps. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlassian ecosystem alias for react-intl@^5.x, a well-known i18n library. This aliasing pattern is consistent across all @atlaskit packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Same-org @atlaskit dependency in a monorepo; may be used via compiled CSS or transitive imports rather than direct JS imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit dependency in a monorepo; design tokens are often consumed via compiled CSS rather than direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit dependency in a monorepo; may be used indirectly. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Atlassian UI component library packages routinely lack marketing-style READMEs and keywords; not indicative of spam or low quality. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with strong track record (238 approved); lack of Sigstore provenance is consistent across their package portfolio. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 5.12.0 | 15 / 9 | |
| 5.11.0 | 15 / 9 | |
| 5.10.1 | 15 / 9 | |
| 5.10.0 | 15 / 9 | |
| 5.9.2 | 15 / 9 | |
| 5.9.1 | 15 / 8 | |
| 5.9.0 | 15 / 8 | |
| 5.8.1 | 15 / 7 | |
| 5.8.0 | 15 / 6 | |
| 5.7.1 | 15 / 6 | |
| 5.7.0 | 15 / 6 | |
| 5.6.0 | 15 / 6 | |
| 5.5.0 | 15 / 6 | |
| 5.4.0 | 15 / 6 | |
| 5.3.0 | 15 / 6 | |
| 5.2.0 | 15 / 6 | |
| 5.1.1 | 15 / 6 | |
| 5.1.0 | 15 / 6 | |
| 5.0.0 | 15 / 6 | |
| 4.19.3 | 16 / 5 | |
| 4.19.2 | 16 / 5 | |
| 4.19.1 | 16 / 5 | |
| 4.19.0 | 16 / 5 | |
| 4.18.1 | 16 / 5 | |
| 4.18.0 | 16 / 5 | |
| 4.17.0 | 16 / 5 | |
| 4.15.0 | 16 / 5 | |
| 4.13.1 | 16 / 5 | |
| 4.12.0 | 16 / 5 | |
| 4.11.1 | 16 / 5 | |
| 4.11.0 | 16 / 5 | |
| 4.10.0 | 16 / 5 | |
| 4.9.0 | 16 / 5 | |
| 4.8.1 | 16 / 5 | |
| 4.8.0 | 16 / 5 | |
| 4.7.0 | 16 / 5 | |
| 4.6.0 | 16 / 5 | |
| 4.5.5 | 16 / 5 | |
| 4.5.4 | 16 / 5 | |
| 4.5.3 | 16 / 5 | |
| 4.5.2 | 16 / 5 | |
| 4.5.1 | 16 / 5 | |
| 4.5.0 | 16 / 5 | |
| 4.4.11 | 15 / 5 | |
| 4.4.10 | 15 / 5 | |
| 4.4.9 | 15 / 5 | |
| 4.4.8 | 15 / 5 | |
| 4.4.7 | 15 / 5 | |
| 4.4.6 | 15 / 5 | |
| 4.4.5 | 15 / 5 | |
| 4.4.4 | 15 / 5 |
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.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.
v5.1.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.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v4.19.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.19.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.19.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.19.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.18.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.18.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.17.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.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.13.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.12.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.11.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.11.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.10.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.9.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.8.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.8.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.7.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.6.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.5.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.
v4.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.
v4.5.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.5.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.5.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.5.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.4.11
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.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.