meilisearch
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): tslib is a standard, trusted TS helper library | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Debug-lib env filter pattern in bundled dep code, not exfiltration. | ai | |
| provenance | missing-githead | AI (provenance): CI publish with SLSA attestation; gitHead absence is a harmless env change for this package. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 0.60.0 | 0 / 17 | |
| 0.59.0 | 0 / 17 | |
| 0.58.0 | 0 / 14 | |
| 0.57.0 | 0 / 14 | |
| 0.56.0 | 0 / 14 | |
| 0.55.0 | 0 / 18 | |
| 0.54.0 | 0 / 18 | |
| 0.53.0 | 0 / 18 | |
| 0.52.0 | 0 / 18 | |
| 0.51.0 | 0 / 18 | |
| 0.50.0 | 0 / 18 | |
| 0.49.0 | 0 / 18 | |
| 0.48.2 | 0 / 18 | |
| 0.48.1 | 0 / 18 | |
| 0.48.0 | 0 / 18 | |
| 0.47.0 | 0 / 31 | |
| 0.46.0 | 0 / 31 | |
| 0.45.0 | 0 / 31 | |
| 0.44.1 | 0 / 31 | |
| 0.44.0 | 0 / 31 | |
| 0.43.0 | 0 / 32 | |
| 0.42.0 | 1 / 32 | |
| 0.41.0 | 1 / 32 | |
| 0.40.0 | 1 / 32 | |
| 0.39.0 | 1 / 32 | |
| 0.38.0 | 1 / 38 | |
| 0.37.0 | 1 / 38 | |
| 0.36.0 | 1 / 37 | |
| 0.35.1 | 1 / 37 | |
| 0.35.0 | 1 / 37 | |
| 0.34.2 | 1 / 37 | |
| 0.34.1 | 1 / 37 | |
| 0.34.0 | 1 / 37 | |
| 0.33.0 | 1 / 37 | |
| 0.32.5 | 1 / 38 | |
| 0.32.4 | 1 / 38 | |
| 0.32.3 | 1 / 38 | |
| 0.32.2 | 1 / 38 | |
| 0.32.1 | 1 / 38 | |
| 0.32.0 | 1 / 38 | |
| 0.31.1 | 1 / 38 | |
| 0.31.0 | 1 / 38 | |
| 0.30.0 | 1 / 36 | |
| 0.29.1 | 1 / 36 | |
| 0.29.0 | 1 / 36 | |
| 0.28.0 | 1 / 36 | |
| 0.27.0 | 1 / 36 | |
| 0.26.0 | 1 / 36 | |
| 0.25.1 | 1 / 35 | |
| 0.25.0 | 1 / 35 | |
| 0.24.0 | 1 / 35 |
v0.60.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.59.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.