@descope-ui/descope-outbound-apps
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @descope-ui monorepo package; no provenance is consistent across all its versions. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-icon | AI (dependencies): Sibling package in the same @descope-ui monorepo scope; consistent versioning pattern. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-avatar | AI (dependencies): Sibling package in the same @descope-ui monorepo scope; consistent versioning pattern. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-button | AI (dependencies): Sibling package in the same @descope-ui monorepo scope; consistent versioning pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo component; missing metadata is typical for internal UI library packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component package; missing description is consistent across the @descope-ui scope. | ai |
Versions (showing 51 of 127)
| Version | Deps | Published |
|---|---|---|
| 3.14.1 | 8 / 2 | |
| 3.14.0 | 8 / 2 | |
| 3.13.3 | 8 / 2 | |
| 3.13.2 | 8 / 2 | |
| 3.13.1 | 8 / 2 | |
| 3.13.0 | 8 / 2 | |
| 3.12.1 | 8 / 2 | |
| 3.12.0 | 8 / 2 | |
| 3.11.8 | 8 / 2 | |
| 3.11.7 | 8 / 2 | |
| 3.11.6 | 8 / 2 | |
| 3.11.5 | 8 / 2 | |
| 3.11.4 | 8 / 2 | |
| 3.11.3 | 8 / 2 | |
| 3.11.2 | 8 / 2 | |
| 3.11.1 | 8 / 2 | |
| 3.11.0 | 8 / 2 | |
| 3.10.2 | 8 / 2 | |
| 3.10.1 | 8 / 2 | |
| 3.10.0 | 8 / 2 | |
| 3.9.2 | 8 / 2 | |
| 3.9.1 | 8 / 2 | |
| 3.9.0 | 8 / 2 | |
| 3.8.0 | 8 / 2 | |
| 3.7.3 | 8 / 2 | |
| 3.7.2 | 8 / 2 | |
| 3.7.1 | 8 / 2 | |
| 3.7.0 | 8 / 2 | |
| 3.6.0 | 8 / 2 | |
| 3.5.1 | 8 / 2 | |
| 3.5.0 | 8 / 2 | |
| 3.4.0 | 8 / 2 | |
| 3.3.5 | 8 / 2 | |
| 3.3.4 | 8 / 2 | |
| 3.3.3 | 8 / 2 | |
| 3.3.2 | 8 / 2 | |
| 3.3.1 | 8 / 2 | |
| 3.3.0 | 8 / 2 | |
| 3.2.2 | 8 / 2 | |
| 3.2.1 | 8 / 2 | |
| 3.2.0 | 8 / 2 | |
| 3.1.13 | 8 / 2 | |
| 3.1.12 | 8 / 2 | |
| 3.1.11 | 8 / 2 | |
| 3.1.10 | 8 / 2 | |
| 3.1.9 | 8 / 2 | |
| 3.1.8 | 8 / 2 | |
| 3.1.7 | 8 / 2 | |
| 3.1.6 | 8 / 2 | |
| 3.1.5 | 8 / 2 | |
| 3.1.4 | 8 / 2 |
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.