@tinacms/search
Full-text search for TinaCMS powered by [search-index](https://github.com/fergiemcdowall/search-index).
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA provenance attestation; expected for monorepo CI publishing. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with documented repo; missing description is benign. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a signal for this package. | ai | |
| dependencies | unvetted-dep:search-index | AI (dependencies): search-index is a legitimate, well-known npm search library; its use is expected in a package named @tinacms/search. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard TinaCMS license declaration pattern used across all packages in the monorepo. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.2.23 | 6 / 7 | |
| 1.2.22 | 6 / 7 | |
| 1.2.21 | 6 / 7 | |
| 1.2.20 | 6 / 7 | |
| 1.2.19 | 6 / 7 | |
| 1.2.18 | 6 / 7 | |
| 1.2.17 | 6 / 7 | |
| 1.2.16 | 6 / 7 | |
| 1.2.15 | 6 / 7 | |
| 1.2.14 | 6 / 7 | |
| 1.2.13 | 6 / 7 | |
| 1.2.12 | 6 / 10 | |
| 1.2.11 | 6 / 10 | |
| 1.2.10 | 6 / 10 | |
| 1.2.9 | 6 / 10 | |
| 1.2.8 | 6 / 10 | |
| 1.2.7 | 6 / 10 | |
| 1.2.6 | 6 / 10 | |
| 1.2.5 | 6 / 10 | |
| 1.2.4 | 6 / 10 | |
| 1.2.3 | 6 / 10 | |
| 1.2.2 | 6 / 10 | |
| 1.2.1 | 6 / 10 | |
| 1.2.0 | 6 / 10 | |
| 1.1.9 | 6 / 10 | |
| 1.1.8 | 6 / 10 | |
| 1.1.7 | 6 / 10 | |
| 1.1.6 | 6 / 10 | |
| 1.1.5 | 6 / 10 | |
| 1.1.4 | 6 / 10 | |
| 1.1.3 | 6 / 10 | |
| 1.1.2 | 6 / 10 | |
| 1.1.1 | 6 / 10 | |
| 1.1.0 | 6 / 10 | |
| 1.0.46 | 6 / 10 | |
| 1.0.45 | 6 / 10 | |
| 1.0.44 | 6 / 10 | |
| 1.0.43 | 6 / 10 | |
| 1.0.42 | 6 / 10 | |
| 1.0.41 | 6 / 10 | |
| 1.0.40 | 6 / 10 | |
| 1.0.39 | 6 / 10 | |
| 1.0.38 | 6 / 10 | |
| 1.0.37 | 6 / 10 | |
| 1.0.36 | 6 / 10 | |
| 1.0.35 | 6 / 10 | |
| 1.0.34 | 6 / 10 | |
| 1.0.33 | 6 / 10 | |
| 1.0.32 | 6 / 10 | |
| 1.0.31 | 6 / 10 | |
| 1.0.30 | 6 / 10 | |
| 1.0.29 | 7 / 10 | |
| 1.0.28 | 7 / 9 | |
| 1.0.27 | 7 / 9 | |
| 1.0.26 | 7 / 9 | |
| 1.0.25 | 7 / 9 | |
| 1.0.24 | 7 / 9 | |
| 1.0.23 | 7 / 9 | |
| 1.0.22 | 7 / 9 | |
| 1.0.21 | 7 / 9 | |
| 1.0.20 | 9 / 9 | |
| 1.0.19 | 9 / 9 |
v1.2.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wicksipedia) than the most recent previously approved version (jeffsee55) on 2024-09-24, but wicksipedia is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.