@robotical/appv2-analytics-gatherer
A tool that gathers data from the Apps and sends it to the Analytics server
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Types-only package from @robotical org; lack of provenance is common and not a meaningful risk here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dep; stable false positive for type-definition packages. | ai | |
| phantom-deps | phantom-dep:bowser | AI (phantom-deps): Config-file reference only; not a real import risk for this types package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.2.18 | 3 / 4 | |
| 1.2.17 | 3 / 4 | |
| 1.2.15 | 3 / 4 | |
| 1.2.14 | 3 / 4 | |
| 1.2.13 | 3 / 4 | |
| 1.2.12 | 3 / 4 | |
| 1.2.11 | 3 / 4 | |
| 1.2.10 | 3 / 4 | |
| 1.2.9 | 3 / 4 | |
| 1.2.8 | 3 / 4 | |
| 1.2.7 | 3 / 4 | |
| 1.2.6 | 3 / 4 | |
| 1.2.5 | 3 / 4 | |
| 1.2.4 | 3 / 4 | |
| 1.2.2 | 3 / 4 | |
| 1.2.1 | 3 / 4 | |
| 1.0.12 | 3 / 4 | |
| 1.0.11 | 3 / 4 | |
| 1.0.10 | 3 / 4 | |
| 1.0.6 | 3 / 4 | |
| 1.0.4 | 3 / 4 | |
| 1.0.2 | 2 / 4 |
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.