@hedystia/swagger
Next-gen TypeScript framework for building type-safe APIs at lightspeed
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA attestation present; gitHead absence is benign when CI/CD provenance is confirmed. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI/CD pipeline explains rapid successive publishes for this package. | ai | |
| provenance | no-provenance | AI (provenance): Publisher uses --provenance flag in release script; absence here is minor and consistent across the package's 112 versions. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 2.3.23 | 3 / 2 | |
| 2.3.22 | 3 / 2 | |
| 2.3.21 | 3 / 2 | |
| 2.3.20 | 3 / 2 | |
| 2.3.19 | 3 / 2 | |
| 2.3.18 | 3 / 2 | |
| 2.3.17 | 3 / 2 | |
| 2.3.9 | 3 / 2 | |
| 2.3.8 | 3 / 2 | |
| 2.3.7 | 3 / 2 | |
| 2.3.6 | 3 / 2 | |
| 2.3.5 | 3 / 2 | |
| 2.3.4 | 3 / 2 | |
| 2.3.3 | 3 / 2 | |
| 2.3.2 | 3 / 2 | |
| 2.3.1 | 3 / 2 | |
| 2.2.13 | 3 / 2 | |
| 2.2.12 | 3 / 2 | |
| 2.2.11 | 3 / 2 | |
| 2.2.9 | 3 / 2 | |
| 2.2.8 | 3 / 2 | |
| 2.2.7 | 3 / 2 | |
| 2.2.6 | 3 / 2 | |
| 2.2.5 | 3 / 2 | |
| 2.2.4 | 3 / 2 | |
| 2.2.3 | 3 / 2 | |
| 2.2.2 | 3 / 2 | |
| 2.2.1 | 3 / 2 | |
| 2.2.0 | 3 / 2 | |
| 2.1.1 | 3 / 1 | |
| 2.1.0 | 3 / 1 | |
| 2.0.14 | 3 / 1 | |
| 2.0.13 | 3 / 1 | |
| 2.0.12 | 3 / 1 | |
| 2.0.11 | 3 / 1 | |
| 2.0.10 | 3 / 1 | |
| 2.0.9 | 3 / 1 | |
| 2.0.8 | 3 / 1 | |
| 2.0.7 | 3 / 1 | |
| 2.0.6 | 3 / 1 | |
| 2.0.5 | 3 / 1 | |
| 2.0.4 | 3 / 1 | |
| 2.0.3 | 3 / 1 | |
| 2.0.2 | 3 / 1 | |
| 2.0.1 | 3 / 1 | |
| 2.0.0 | 3 / 1 | |
| 1.10.5 | 3 / 1 | |
| 1.10.4 | 3 / 1 | |
| 1.10.3 | 3 / 1 | |
| 1.10.2 | 3 / 1 | |
| 1.10.1 | 3 / 2 | |
| 1.10.0 | 3 / 2 | |
| 1.9.10 | 3 / 2 | |
| 1.9.9 | 3 / 2 | |
| 1.9.8 | 3 / 2 | |
| 1.9.7 | 3 / 2 | |
| 1.9.6 | 3 / 2 | |
| 1.9.5 | 3 / 2 | |
| 1.9.4 | 3 / 2 | |
| 1.9.3 | 3 / 2 | |
| 1.9.2 | 3 / 2 | |
| 1.9.1 | 3 / 2 | |
| 1.9.0 | 3 / 2 | |
| 1.8.0 | 3 / 2 | |
| 1.7.8 | 3 / 2 | |
| 1.7.7 | 3 / 2 | |
| 1.7.6 | 3 / 2 | |
| 1.7.5 | 3 / 2 | |
| 1.7.4 | 3 / 2 | |
| 1.7.3 | 3 / 2 | |
| 1.7.2 | 3 / 2 | |
| 1.7.1 | 3 / 2 | |
| 1.7.0 | 3 / 2 | |
| 1.6.10 | 3 / 2 | |
| 1.6.9 | 3 / 2 | |
| 1.6.8 | 3 / 2 | |
| 1.6.7 | 3 / 2 |
v2.3.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.22
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.3.21
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: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.20
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: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.19
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: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.18
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: zastinian.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v1.10.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v1.10.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.
v1.10.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zastinian.