@launchpad-ui/filter
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:@launchpad-ui/dropdown | AI (phantom-deps): Same-org sibling package in monorepo; phantom-dep heuristic is a stable false positive here. | ai | |
| provenance | publisher-changed | AI (provenance): LaunchDarkly migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD origin. | ai | |
| phantom-deps | phantom-dep:classix | AI (phantom-deps): Monorepo build tool dependency; referenced in config, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/menu | AI (phantom-deps): Same-org sibling package in monorepo; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/icons | AI (phantom-deps): Same-org sibling package in monorepo; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/button | AI (phantom-deps): Same-org sibling package in monorepo; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/tooltip | AI (phantom-deps): Same-org sibling package in monorepo; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/tokens | AI (phantom-deps): Same-org monorepo dep; declared in dependencies, phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.11.17 | 7 / 3 | |
| 0.11.16 | 7 / 3 | |
| 0.11.15 | 7 / 3 | |
| 0.11.14 | 7 / 3 | |
| 0.11.13 | 7 / 3 | |
| 0.11.12 | 7 / 3 | |
| 0.11.11 | 7 / 3 | |
| 0.11.10 | 7 / 3 | |
| 0.11.9 | 7 / 3 | |
| 0.11.8 | 7 / 3 | |
| 0.11.7 | 7 / 3 | |
| 0.11.6 | 7 / 3 | |
| 0.11.5 | 7 / 3 | |
| 0.11.4 | 7 / 3 | |
| 0.11.3 | 7 / 3 | |
| 0.11.2 | 7 / 3 | |
| 0.11.1 | 7 / 3 | |
| 0.11.0 | 7 / 3 | |
| 0.10.0 | 7 / 3 | |
| 0.9.0 | 7 / 3 | |
| 0.8.4 | 7 / 3 | |
| 0.8.3 | 7 / 3 | |
| 0.8.2 | 7 / 3 | |
| 0.8.1 | 7 / 3 | |
| 0.8.0 | 7 / 3 | |
| 0.7.64 | 8 / 2 | |
| 0.7.63 | 8 / 2 | |
| 0.7.62 | 8 / 2 | |
| 0.7.61 | 8 / 2 | |
| 0.7.60 | 8 / 2 | |
| 0.7.59 | 8 / 2 | |
| 0.7.58 | 8 / 2 | |
| 0.7.57 | 8 / 2 | |
| 0.7.56 | 8 / 2 | |
| 0.7.55 | 8 / 2 | |
| 0.7.54 | 8 / 2 | |
| 0.7.53 | 8 / 2 | |
| 0.7.52 | 8 / 2 | |
| 0.7.51 | 8 / 2 | |
| 0.7.50 | 8 / 2 | |
| 0.7.49 | 8 / 2 | |
| 0.7.48 | 8 / 2 | |
| 0.7.47 | 8 / 2 | |
| 0.7.46 | 8 / 2 | |
| 0.7.45 | 8 / 2 | |
| 0.7.44 | 8 / 2 | |
| 0.7.43 | 8 / 2 | |
| 0.7.42 | 8 / 2 | |
| 0.7.41 | 8 / 2 | |
| 0.7.40 | 8 / 2 | |
| 0.7.39 | 8 / 2 | |
| 0.7.38 | 8 / 2 | |
| 0.7.37 | 8 / 2 | |
| 0.7.36 | 8 / 2 | |
| 0.7.35 | 8 / 2 | |
| 0.7.34 | 8 / 2 | |
| 0.7.33 | 8 / 2 | |
| 0.7.32 | 8 / 2 | |
| 0.7.31 | 8 / 2 | |
| 0.7.30 | 8 / 2 | |
| 0.7.29 | 8 / 2 | |
| 0.7.28 | 8 / 2 | |
| 0.7.27 | 8 / 2 | |
| 0.7.26 | 8 / 2 | |
| 0.7.25 | 8 / 2 | |
| 0.7.24 | 8 / 2 | |
| 0.7.23 | 8 / 2 | |
| 0.7.22 | 8 / 2 | |
| 0.7.21 | 8 / 2 | |
| 0.7.20 | 8 / 2 | |
| 0.7.19 | 8 / 2 | |
| 0.7.18 | 8 / 2 | |
| 0.7.17 | 8 / 2 | |
| 0.7.16 | 8 / 2 | |
| 0.7.15 | 8 / 2 | |
| 0.7.14 | 8 / 2 | |
| 0.7.13 | 8 / 2 | |
| 0.7.12 | 8 / 2 | |
| 0.7.11 | 8 / 2 |
v0.11.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.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.