@descope-ui/descope-attachment
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
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): Monorepo component package; missing description is a stable pattern across this org's packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across this org's packages; consistent pattern, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing metadata is typical for internal scoped packages, not spam. | ai | |
| phantom-deps | phantom-dep:@descope-ui/theme-globals | AI (phantom-deps): Same org scope; likely used via CSS/theme imports not caught by static import analysis. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 3.18.2 | 3 / 5 | |
| 3.18.1 | 3 / 5 | |
| 3.18.0 | 3 / 5 | |
| 3.17.0 | 3 / 5 | |
| 3.16.4 | 3 / 5 | |
| 3.16.3 | 3 / 5 | |
| 3.16.2 | 3 / 4 | |
| 3.16.1 | 3 / 4 | |
| 3.16.0 | 3 / 4 | |
| 3.15.2 | 3 / 4 | |
| 3.15.1 | 3 / 4 | |
| 3.15.0 | 3 / 4 | |
| 3.14.10 | 3 / 4 | |
| 3.14.9 | 3 / 4 | |
| 3.14.8 | 3 / 4 | |
| 3.14.7 | 3 / 4 | |
| 3.14.6 | 3 / 4 | |
| 3.14.5 | 3 / 4 | |
| 3.14.4 | 3 / 4 | |
| 3.14.3 | 3 / 4 | |
| 3.14.2 | 3 / 4 | |
| 3.14.1 | 3 / 4 | |
| 3.14.0 | 3 / 4 | |
| 3.13.3 | 3 / 4 | |
| 3.13.2 | 3 / 4 | |
| 3.13.1 | 3 / 4 | |
| 3.13.0 | 3 / 4 | |
| 3.12.1 | 3 / 4 | |
| 3.12.0 | 3 / 4 | |
| 3.11.8 | 3 / 4 | |
| 3.11.7 | 3 / 4 | |
| 3.11.6 | 3 / 4 | |
| 3.11.5 | 3 / 4 | |
| 3.11.4 | 3 / 4 | |
| 3.11.3 | 3 / 4 | |
| 3.11.2 | 3 / 4 | |
| 3.11.1 | 3 / 4 | |
| 3.11.0 | 3 / 4 | |
| 3.10.2 | 3 / 4 | |
| 3.10.1 | 3 / 4 | |
| 3.10.0 | 3 / 4 | |
| 3.9.2 | 3 / 4 | |
| 3.9.1 | 3 / 4 | |
| 3.9.0 | 3 / 4 | |
| 3.8.0 | 3 / 4 | |
| 3.7.3 | 3 / 4 | |
| 3.7.2 | 3 / 4 | |
| 3.7.1 | 3 / 4 | |
| 3.7.0 | 2 / 4 | |
| 3.6.0 | 2 / 4 | |
| 3.5.1 | 2 / 4 | |
| 3.5.0 | 2 / 4 | |
| 3.4.0 | 2 / 4 | |
| 3.3.5 | 2 / 4 | |
| 3.3.4 | 2 / 4 | |
| 3.3.3 | 2 / 4 | |
| 3.3.1 | 2 / 4 | |
| 3.3.0 | 2 / 4 | |
| 3.2.2 | 2 / 4 | |
| 3.2.1 | 2 / 4 | |
| 3.2.0 | 2 / 4 |
v3.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.