@trackunit/filters-filter-bar
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): 940-day-old org package with 1360 versions; sparse README is a documentation issue, not spam/phishing. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all Trackunit org packages; not a per-version risk signal. | ai |
Versions (showing 51 of 888)
| Version | Deps | Published |
|---|---|---|
| 2.2.23 | 15 / 0 | |
| 2.2.22 | 15 / 0 | |
| 2.2.21 | 15 / 0 | |
| 2.2.20 | 15 / 0 | |
| 2.2.19 | 15 / 0 | |
| 2.2.17 | 15 / 0 | |
| 2.2.15 | 15 / 0 | |
| 2.2.9 | 15 / 0 | |
| 2.2.8 | 15 / 0 | |
| 2.2.7 | 15 / 0 | |
| 2.2.6 | 15 / 0 | |
| 2.2.5 | 15 / 0 | |
| 2.2.4 | 15 / 0 | |
| 2.2.3 | 15 / 0 | |
| 2.2.2 | 15 / 0 | |
| 2.2.1 | 15 / 0 | |
| 2.2.0 | 15 / 0 | |
| 2.1.70 | 15 / 0 | |
| 2.1.69 | 15 / 0 | |
| 2.1.68 | 15 / 0 | |
| 2.1.67 | 15 / 0 | |
| 2.1.66 | 15 / 0 | |
| 2.1.65 | 15 / 0 | |
| 2.1.64 | 15 / 0 | |
| 2.1.63 | 15 / 0 | |
| 2.1.62 | 15 / 0 | |
| 2.1.61 | 15 / 0 | |
| 2.1.60 | 15 / 0 | |
| 2.1.59 | 15 / 0 | |
| 2.1.58 | 15 / 0 | |
| 2.1.56 | 15 / 0 | |
| 2.1.55 | 15 / 0 | |
| 2.1.53 | 15 / 0 | |
| 2.1.52 | 15 / 0 | |
| 2.1.51 | 15 / 0 | |
| 2.1.50 | 15 / 0 | |
| 2.1.49 | 15 / 0 | |
| 2.1.48 | 15 / 0 | |
| 2.1.47 | 15 / 0 | |
| 2.1.46 | 15 / 0 | |
| 2.1.44 | 15 / 0 | |
| 2.1.43 | 15 / 0 | |
| 2.1.42 | 15 / 0 | |
| 2.1.41 | 15 / 0 | |
| 2.1.39 | 15 / 0 | |
| 2.1.38 | 15 / 0 | |
| 2.1.37 | 15 / 0 | |
| 2.1.36 | 15 / 0 | |
| 2.1.35 | 15 / 0 | |
| 2.1.34 | 15 / 0 | |
| 2.1.33 | 15 / 0 |
v2.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.