@cdc/filtered-text
React component for adding filtered text on dashboards.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): CDC monorepo package; provenance not configured for this org's npm publishing pipeline. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash referenced in config files only, not a real import gap for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.26.6 | 3 / 5 | |
| 4.26.5 | 3 / 5 | |
| 4.26.4 | 3 / 5 | |
| 4.26.3 | 3 / 5 | |
| 4.26.2 | 3 / 5 | |
| 4.26.1 | 3 / 5 | |
| 4.25.11 | 3 / 4 | |
| 4.25.10 | 3 / 5 | |
| 4.25.8 | 1 / 0 | |
| 4.25.7 | 1 / 0 | |
| 4.25.6 | 1 / 0 | |
| 4.25.3 | 3 / 0 | |
| 4.25.1 | 3 / 0 | |
| 4.24.12 | 3 / 0 | |
| 4.24.11 | 3 / 0 | |
| 4.24.10 | 3 / 0 | |
| 4.24.9 | 3 / 0 | |
| 4.24.7 | 3 / 0 | |
| 4.24.5 | 3 / 0 | |
| 4.24.4 | 3 / 0 |
v4.26.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.