@interopio/desktop
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@interopio/insights-logs | AI (phantom-deps): Same org scope; consistent with other accepted phantom-dep patterns in this package. | ai | |
| phantom-deps | phantom-dep:@interopio/insights-instrumentations-web | AI (phantom-deps): Same org scope; consistent with other accepted phantom-dep patterns in this package. | ai | |
| phantom-deps | phantom-dep:@interopio/utils | AI (phantom-deps): Same-org dep likely re-exported via bundle; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@interopio/insights-base | AI (phantom-deps): Same-org dep likely re-exported via bundle; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@interopio/insights-traces | AI (phantom-deps): Same-org dep likely re-exported via bundle; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@interopio/insights-metrics | AI (phantom-deps): Same-org dep likely re-exported via bundle; stable FP for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 6.21.0 | 8 / 2 | |
| 6.20.4 | 8 / 1 | |
| 6.20.3 | 8 / 1 | |
| 6.20.2 | 8 / 1 | |
| 6.20.1 | 8 / 1 | |
| 6.20.0 | 8 / 1 | |
| 6.19.0 | 10 / 1 | |
| 6.18.0 | 5 / 0 | |
| 6.17.0 | 5 / 0 | |
| 6.16.3 | 5 / 0 | |
| 6.16.2 | 5 / 0 | |
| 6.16.1 | 5 / 0 | |
| 6.16.0 | 5 / 0 |
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.