@toptal/picasso-password-input
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@toptal/picasso-icons | AI (dependencies): Same-org monorepo sibling; stable pattern across all Picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Same-org monorepo sibling; stable pattern across all Picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-button | AI (dependencies): Same-org monorepo sibling; stable pattern across all Picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-outlined-input | AI (dependencies): Same-org monorepo sibling; stable pattern across all Picasso packages. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-input-adornment | AI (dependencies): Same-org monorepo sibling; stable pattern across all Picasso packages. | ai | |
| phantom-deps | phantom-dep:@toptal/picasso-utils | AI (phantom-deps): Same-org monorepo dep; may be re-exported via sibling rather than directly imported. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.1.13 | 5 / 2 | |
| 5.1.12 | 5 / 2 | |
| 5.1.11 | 5 / 2 | |
| 5.1.8 | 5 / 2 | |
| 5.1.2 | 5 / 2 | |
| 5.1.1 | 5 / 2 | |
| 5.1.0 | 5 / 2 |
v5.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.