@contentstack/types-generator
Contentstack type definition generation library
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is the Contentstack org account with 78 approved packages; dormancy is consistent with infrequent but legitimate maintenance cadence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @contentstack/cli-utilities; consistent with the package's Contentstack ecosystem context. | ai | |
| dependencies | unvetted-dep:@gql2ts/from-schema | AI (dependencies): @gql2ts/from-schema is a known GraphQL codegen utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Contentstack package; lack of provenance is consistent across all 28 versions and is not a risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 6 / 15 | |
| 3.9.5 | 6 / 15 | |
| 3.9.4 | 6 / 15 | |
| 3.9.3 | 6 / 15 | |
| 3.9.1 | 6 / 15 | |
| 3.9.0 | 6 / 15 | |
| 3.8.0 | 6 / 15 | |
| 3.6.0 | 7 / 14 | |
| 3.5.0 | 7 / 14 | |
| 3.4.0 | 7 / 14 | |
| 3.2.0 | 6 / 14 | |
| 3.1.0 | 6 / 14 | |
| 3.0.0 | 6 / 14 |
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.