@atlaskit/rovo-agent-analytics
Rovo Agents analytics
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Same-org scoped package loaded by Atlassian monorepo convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package commonly loaded by Babel convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org scoped package loaded by Atlassian monorepo convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Same-org scoped package loaded by Atlassian monorepo convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@compiled/react | AI (phantom-deps): @compiled/react is explicitly declared as a runtime dependency in package.json and used for CSS-in-JS styling; the phantom-dep finding is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): atlassianartifactteam is a well-established Atlassian publisher with 257 approved packages; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 4 / 7 | |
| 2.2.0 | 4 / 7 | |
| 2.1.1 | 4 / 7 | |
| 2.1.0 | 4 / 7 | |
| 2.0.0 | 4 / 7 | |
| 1.11.0 | 4 / 7 | |
| 1.10.0 | 4 / 7 | |
| 1.9.0 | 4 / 7 | |
| 1.8.0 | 4 / 6 | |
| 1.7.0 | 4 / 6 | |
| 1.6.0 | 4 / 6 | |
| 1.5.0 | 4 / 6 | |
| 1.4.0 | 4 / 6 | |
| 1.3.0 | 4 / 6 | |
| 1.2.0 | 4 / 6 | |
| 1.1.1 | 4 / 6 | |
| 1.1.0 | 4 / 5 | |
| 1.0.0 | 4 / 5 | |
| 0.20.0 | 4 / 5 | |
| 0.19.0 | 4 / 5 | |
| 0.18.0 | 4 / 5 | |
| 0.17.0 | 4 / 5 | |
| 0.16.0 | 4 / 5 | |
| 0.15.1 | 4 / 5 | |
| 0.15.0 | 4 / 5 | |
| 0.14.0 | 4 / 5 | |
| 0.13.0 | 4 / 5 | |
| 0.12.1 | 4 / 5 | |
| 0.12.0 | 4 / 5 | |
| 0.11.0 | 4 / 5 | |
| 0.10.0 | 4 / 5 | |
| 0.9.0 | 4 / 5 | |
| 0.8.0 | 4 / 5 | |
| 0.7.0 | 4 / 5 | |
| 0.6.0 | 4 / 5 | |
| 0.5.0 | 4 / 5 | |
| 0.4.0 | 4 / 5 | |
| 0.3.0 | 7 / 5 | |
| 0.2.0 | 7 / 5 | |
| 0.1.0 | 5 / 5 |
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.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.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.4.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.
v0.3.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.
v0.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.
v0.1.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.