@auth0/quantum-product
Quantum Product is a reusable component library that helps Auth0 teams build UIs faster. The goal is to make building durable UIs more productive and satisfying.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@auth0/quantum-icons | AI (dependencies): Sibling package in the Auth0/Okta quantum design system monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@auth0/quantum-tokens | AI (dependencies): Sibling package in the Auth0/Okta quantum design system monorepo; expected dependency. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 2.15.3 | 8 / 0 | |
| 2.15.2 | 8 / 0 | |
| 2.15.1 | 8 / 0 | |
| 2.15.0 | 8 / 0 | |
| 2.14.0 | 8 / 0 | |
| 2.13.0 | 8 / 0 | |
| 2.12.0 | 8 / 0 | |
| 2.11.0 | 8 / 0 | |
| 2.10.8 | 8 / 0 | |
| 2.10.7 | 8 / 0 | |
| 2.10.6 | 8 / 0 | |
| 2.10.5 | 8 / 0 | |
| 2.10.4 | 8 / 0 | |
| 2.10.3 | 8 / 0 | |
| 2.10.2 | 8 / 0 | |
| 2.10.1 | 8 / 0 | |
| 2.10.0 | 8 / 0 | |
| 2.9.7 | 8 / 0 | |
| 2.9.5 | 8 / 0 | |
| 2.9.4 | 8 / 0 | |
| 2.9.3 | 8 / 0 | |
| 2.9.2 | 8 / 0 | |
| 2.6.0 | 8 / 0 | |
| 2.5.9 | 8 / 0 | |
| 2.5.8 | 7 / 0 | |
| 2.5.7 | 7 / 0 | |
| 2.5.6 | 7 / 0 | |
| 2.5.5 | 7 / 0 | |
| 2.5.4 | 7 / 0 | |
| 2.5.3 | 7 / 0 | |
| 2.5.2 | 7 / 0 | |
| 2.5.1 | 7 / 0 | |
| 2.5.0 | 7 / 0 | |
| 2.4.11 | 7 / 0 | |
| 2.4.10 | 7 / 0 | |
| 2.4.9 | 7 / 0 | |
| 2.4.8 | 7 / 0 | |
| 2.4.7 | 7 / 0 | |
| 2.4.6 | 7 / 0 | |
| 2.4.5 | 7 / 0 | |
| 2.4.4 | 7 / 0 | |
| 2.4.3 | 7 / 0 | |
| 2.4.2 | 7 / 0 | |
| 2.4.1 | 7 / 0 | |
| 2.4.0 | 7 / 0 | |
| 2.3.0 | 7 / 0 | |
| 2.2.0 | 7 / 0 | |
| 2.1.5 | 7 / 0 | |
| 2.1.4 | 7 / 0 | |
| 2.1.3 | 7 / 0 | |
| 2.1.2 | 7 / 0 | |
| 2.1.1 | 7 / 0 | |
| 2.1.0 | 7 / 0 | |
| 2.0.0 | 8 / 0 |
v2.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.