@atlaskit/link-test-helpers
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with a strong track record; lack of Sigstore provenance is consistent across their entire package portfolio. | 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 Atlassian ecosystem and poses no real risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Atlaskit monorepo packages routinely have minimal READMEs and no keywords; this is a test-helpers package, not a standalone library. Not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same @atlaskit org scope; declared but not directly imported is expected in a monorepo test-helper package with transitive deps. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 10.3.0 | 11 / 3 | |
| 10.2.2 | 11 / 2 | |
| 10.2.1 | 11 / 2 | |
| 10.2.0 | 11 / 2 | |
| 10.1.0 | 11 / 2 | |
| 10.0.0 | 11 / 2 | |
| 9.1.0 | 12 / 1 | |
| 9.0.2 | 12 / 1 | |
| 9.0.1 | 12 / 1 | |
| 9.0.0 | 12 / 1 | |
| 8.5.1 | 12 / 1 | |
| 8.5.0 | 12 / 1 |
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.