@digigov/text-search
@digigov text-search
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): 166-version package with active CI pipeline; rapid publishes are consistent with automated release workflow. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 1 / 0 | |
| 2.4.2 | 1 / 0 | |
| 2.4.1 | 1 / 0 | |
| 2.4.0 | 1 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.3 | 1 / 0 | |
| 2.2.1 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.14 | 1 / 0 | |
| 2.0.8 | 1 / 0 | |
| 2.0.7 | 1 / 0 | |
| 2.0.6 | 1 / 0 | |
| 2.0.3 | 1 / 0 | |
| 2.0.2 | 1 / 0 |
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.