@launchpad-ui/form
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@react-stately/numberfield | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/button | AI (phantom-deps): Same org scope monorepo package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/tooltip | AI (phantom-deps): Same org scope monorepo package; stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): LaunchDarkly migrated to GitHub Actions CI publishing; SLSA provenance attestation confirms trusted pipeline. | ai | |
| phantom-deps | phantom-dep:classix | AI (phantom-deps): Same-org monorepo; referenced in config files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/icons | AI (phantom-deps): Same org scope monorepo package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/tokens | AI (phantom-deps): Same org scope; tokens likely used via CSS/type imports not caught by static import analysis. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @launchpad-ui org package; Levenshtein match to 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.15.17 | 6 / 3 | |
| 0.15.16 | 6 / 3 | |
| 0.15.15 | 6 / 3 | |
| 0.15.14 | 6 / 6 | |
| 0.15.13 | 6 / 6 | |
| 0.15.12 | 6 / 6 | |
| 0.15.11 | 6 / 6 | |
| 0.15.10 | 6 / 6 | |
| 0.15.9 | 6 / 6 | |
| 0.15.8 | 6 / 6 | |
| 0.15.7 | 6 / 6 | |
| 0.15.6 | 6 / 6 | |
| 0.15.5 | 6 / 6 | |
| 0.15.4 | 6 / 6 | |
| 0.15.3 | 6 / 6 | |
| 0.15.2 | 6 / 6 | |
| 0.15.1 | 6 / 6 | |
| 0.15.0 | 6 / 6 | |
| 0.14.0 | 6 / 6 | |
| 0.13.0 | 6 / 6 | |
| 0.12.4 | 6 / 6 | |
| 0.12.3 | 6 / 6 | |
| 0.12.2 | 6 / 6 | |
| 0.12.1 | 6 / 6 | |
| 0.12.0 | 6 / 6 | |
| 0.11.64 | 10 / 2 | |
| 0.11.63 | 10 / 2 | |
| 0.11.62 | 10 / 2 | |
| 0.11.61 | 10 / 2 | |
| 0.11.60 | 10 / 2 | |
| 0.11.59 | 10 / 2 | |
| 0.11.58 | 10 / 2 | |
| 0.11.57 | 10 / 2 | |
| 0.11.56 | 10 / 2 | |
| 0.11.55 | 10 / 2 | |
| 0.11.54 | 10 / 2 | |
| 0.11.53 | 10 / 2 | |
| 0.11.52 | 10 / 2 | |
| 0.11.51 | 10 / 2 | |
| 0.11.50 | 10 / 2 | |
| 0.11.49 | 10 / 2 | |
| 0.11.48 | 10 / 2 | |
| 0.11.47 | 10 / 2 | |
| 0.11.46 | 10 / 2 | |
| 0.11.45 | 10 / 2 | |
| 0.11.44 | 10 / 2 | |
| 0.11.43 | 10 / 2 | |
| 0.11.42 | 10 / 2 | |
| 0.11.41 | 10 / 2 | |
| 0.11.40 | 10 / 2 | |
| 0.11.39 | 10 / 2 | |
| 0.11.38 | 10 / 2 | |
| 0.11.37 | 10 / 2 | |
| 0.11.36 | 10 / 2 | |
| 0.11.35 | 10 / 2 | |
| 0.11.34 | 10 / 2 | |
| 0.11.33 | 10 / 2 | |
| 0.11.32 | 10 / 2 | |
| 0.11.31 | 10 / 2 | |
| 0.11.30 | 10 / 2 | |
| 0.11.29 | 10 / 2 | |
| 0.11.28 | 10 / 2 | |
| 0.11.27 | 10 / 2 | |
| 0.11.26 | 10 / 2 | |
| 0.11.25 | 10 / 2 | |
| 0.11.24 | 10 / 2 | |
| 0.11.23 | 10 / 2 | |
| 0.11.22 | 10 / 2 | |
| 0.11.21 | 10 / 2 | |
| 0.11.20 | 10 / 2 | |
| 0.11.19 | 10 / 2 | |
| 0.11.18 | 10 / 2 | |
| 0.11.17 | 10 / 2 | |
| 0.11.16 | 10 / 2 | |
| 0.11.15 | 10 / 2 | |
| 0.11.14 | 10 / 2 | |
| 0.11.13 | 10 / 2 | |
| 0.11.12 | 10 / 2 | |
| 0.11.11 | 10 / 2 |
v0.15.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.