@voicenter-team/real-time-events-types
## Description This project automates the generation of TypeScript types and enums using `openapi-typescript-codegen` from a Swagger JSON file (`data/Swagger.json`). All generated types will be placed in the `dist` folder.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): No behavioral change accompanies the maintainer swap; likely internal team rotation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with zero-diff release is benign for a low-traffic internal types package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 0.0.29 | 0 / 5 | |
| 0.0.28 | 0 / 5 | |
| 0.0.27 | 0 / 5 | |
| 0.0.26 | 0 / 5 | |
| 0.0.25 | 0 / 5 | |
| 0.0.24 | 0 / 5 | |
| 0.0.23 | 0 / 5 | |
| 0.0.22 | 0 / 5 | |
| 0.0.21 | 0 / 5 | |
| 0.0.20 | 0 / 5 | |
| 0.0.19 | 0 / 5 | |
| 0.0.18 | 0 / 5 | |
| 0.0.17 | 0 / 5 | |
| 0.0.16 | 0 / 5 | |
| 0.0.15 | 0 / 5 | |
| 0.0.14 | 0 / 5 | |
| 0.0.13 | 0 / 5 | |
| 0.0.12 | 0 / 5 | |
| 0.0.11 | 0 / 5 | |
| 0.0.10 | 0 / 5 | |
| 0.0.9 | 0 / 5 | |
| 0.0.8 | 0 / 5 | |
| 0.0.7 | 0 / 5 | |
| 0.0.6 | 0 / 5 | |
| 0.0.5 | 0 / 5 | |
| 0.0.4 | 0 / 5 | |
| 0.0.3 | 0 / 5 | |
| 0.0.2 | 0 / 5 | |
| 0.0.1 | 0 / 5 |
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.