@inkeep/agents-ui-cloud
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Proprietary commercial package; empty description is consistent across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance is consistent across the version history. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Commercial SDK with proprietary license; sparse README/metadata is expected for an enterprise-facing package, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Peer/bundled dep pattern for UI library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-use-controllable-state | AI (phantom-deps): Peer/bundled dep pattern for UI library; stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.17.1 | 3 / 21 | |
| 0.17.0 | 3 / 21 | |
| 0.16.5 | 3 / 21 | |
| 0.16.4 | 3 / 21 | |
| 0.16.3 | 3 / 21 | |
| 0.16.2 | 3 / 21 | |
| 0.16.1 | 3 / 21 | |
| 0.16.0 | 3 / 21 | |
| 0.15.30 | 3 / 21 | |
| 0.15.29 | 3 / 21 | |
| 0.15.28 | 3 / 21 | |
| 0.15.27 | 3 / 21 | |
| 0.15.26 | 3 / 21 | |
| 0.15.25 | 3 / 21 | |
| 0.15.24 | 3 / 21 | |
| 0.15.23 | 3 / 21 | |
| 0.15.22 | 3 / 21 | |
| 0.15.21 | 3 / 21 | |
| 0.15.20 | 3 / 21 | |
| 0.15.19 | 3 / 21 | |
| 0.15.18 | 3 / 21 | |
| 0.15.17 | 3 / 21 | |
| 0.15.16 | 3 / 21 | |
| 0.15.15 | 3 / 21 | |
| 0.15.14 | 3 / 21 |
v0.17.1
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.17
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.15.16
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.15.15
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.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.