@grest-ts/config
Configuration management for Grest Framework - resources, secrets, and settings
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @grest-ts packages; not a risk indicator for this monorepo. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.0.70 | 0 / 1 | |
| 0.0.69 | 0 / 1 | |
| 0.0.68 | 0 / 1 | |
| 0.0.67 | 0 / 1 | |
| 0.0.66 | 0 / 1 | |
| 0.0.65 | 0 / 1 | |
| 0.0.64 | 0 / 1 | |
| 0.0.63 | 0 / 1 | |
| 0.0.62 | 0 / 1 | |
| 0.0.61 | 0 / 1 | |
| 0.0.60 | 0 / 1 | |
| 0.0.59 | 0 / 1 | |
| 0.0.58 | 0 / 1 | |
| 0.0.56 | 0 / 1 | |
| 0.0.55 | 0 / 1 | |
| 0.0.52 | 0 / 1 | |
| 0.0.51 | 0 / 1 | |
| 0.0.50 | 0 / 1 | |
| 0.0.49 | 0 / 1 | |
| 0.0.48 | 0 / 1 | |
| 0.0.47 | 0 / 1 | |
| 0.0.46 | 0 / 1 | |
| 0.0.45 | 0 / 1 | |
| 0.0.44 | 0 / 1 | |
| 0.0.43 | 0 / 1 | |
| 0.0.42 | 0 / 1 | |
| 0.0.39 | 0 / 1 | |
| 0.0.38 | 0 / 1 | |
| 0.0.37 | 0 / 1 | |
| 0.0.36 | 0 / 1 | |
| 0.0.35 | 0 / 1 | |
| 0.0.34 | 0 / 1 | |
| 0.0.33 | 0 / 1 | |
| 0.0.32 | 0 / 1 | |
| 0.0.31 | 0 / 1 | |
| 0.0.29 | 3 / 1 | |
| 0.0.28 | 3 / 1 | |
| 0.0.27 | 3 / 1 | |
| 0.0.26 | 3 / 1 | |
| 0.0.25 | 3 / 1 | |
| 0.0.24 | 3 / 1 | |
| 0.0.23 | 3 / 1 | |
| 0.0.22 | 3 / 1 | |
| 0.0.21 | 3 / 1 | |
| 0.0.20 | 3 / 1 | |
| 0.0.19 | 3 / 1 | |
| 0.0.18 | 3 / 1 | |
| 0.0.17 | 3 / 1 | |
| 0.0.16 | 3 / 1 | |
| 0.0.14 | 3 / 2 | |
| 0.0.13 | 3 / 2 |
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.