@atlaskit/afm-i18n-platform-ai-mate-rovo-agent-components
NPM i18n package for AFM platform-ai-mate-rovo-agent-components published by Traduki
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is in build.js, a build-time script run during prepublishOnly — not an install hook or runtime dep. Standard pattern for Atlassian i18n build tooling. | ai | |
| provenance | no-provenance | AI (provenance): Established Atlassian package with 102 versions and strong publisher track record; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 58 of 158)
| Version | Deps | Published |
|---|---|---|
| 2.59.0 | 0 / 1 | |
| 2.58.0 | 0 / 1 | |
| 2.57.0 | 0 / 1 | |
| 2.56.0 | 0 / 1 | |
| 2.55.0 | 0 / 1 | |
| 2.54.0 | 0 / 1 | |
| 2.53.0 | 0 / 1 | |
| 2.52.0 | 0 / 1 | |
| 2.51.0 | 0 / 1 | |
| 2.50.0 | 0 / 1 | |
| 2.49.0 | 0 / 1 | |
| 2.48.0 | 0 / 1 | |
| 2.47.0 | 0 / 1 | |
| 2.46.0 | 0 / 1 | |
| 2.45.0 | 0 / 1 | |
| 2.44.0 | 0 / 1 | |
| 2.43.0 | 0 / 1 | |
| 2.42.0 | 0 / 1 | |
| 2.41.0 | 0 / 1 | |
| 2.40.0 | 0 / 1 | |
| 2.39.0 | 0 / 1 | |
| 2.38.0 | 0 / 1 | |
| 2.37.0 | 0 / 1 | |
| 2.36.0 | 0 / 1 | |
| 2.35.0 | 0 / 1 | |
| 2.34.0 | 0 / 1 | |
| 2.33.0 | 0 / 1 | |
| 2.32.0 | 0 / 1 | |
| 2.31.0 | 0 / 1 | |
| 2.30.0 | 0 / 1 | |
| 2.29.0 | 0 / 1 | |
| 2.28.0 | 0 / 1 | |
| 2.27.0 | 0 / 1 | |
| 2.26.0 | 0 / 1 | |
| 2.25.0 | 0 / 1 | |
| 2.24.0 | 0 / 1 | |
| 2.23.0 | 0 / 1 | |
| 2.22.0 | 0 / 1 | |
| 2.21.0 | 0 / 1 | |
| 2.20.0 | 0 / 1 | |
| 2.19.0 | 0 / 1 | |
| 2.18.0 | 0 / 1 | |
| 2.17.0 | 0 / 1 | |
| 2.16.0 | 0 / 1 | |
| 2.15.0 | 0 / 1 | |
| 2.14.0 | 0 / 1 | |
| 2.13.0 | 0 / 1 | |
| 2.12.0 | 0 / 1 | |
| 2.11.0 | 0 / 1 | |
| 2.10.0 | 0 / 1 | |
| 2.9.0 | 0 / 1 | |
| 2.8.0 | 0 / 1 | |
| 2.7.0 | 0 / 1 | |
| 2.6.0 | 0 / 1 | |
| 2.5.0 | 0 / 1 | |
| 2.4.0 | 0 / 1 | |
| 2.3.0 | 0 / 1 | |
| 2.2.0 | 0 / 1 |
v2.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.