@kitschpatrol/create-project
Kitschpatrol's TypeScript project templates.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Low-download scaffolding tool; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:bingo | AI (phantom-deps): Template scaffolding tool; bingo is a framework dep used in template context, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:bingo-fs | AI (phantom-deps): Template scaffolding tool; bingo-fs is a framework dep used in template context, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:bingo-handlebars | AI (phantom-deps): Template scaffolding tool; bingo-handlebars is a framework dep used in template context, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Referenced in config/template context; stable false positive for this scaffolding package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 4 / 9 | |
| 1.5.1 | 4 / 9 | |
| 1.5.0 | 4 / 9 | |
| 1.4.0 | 4 / 9 | |
| 1.3.2 | 4 / 9 | |
| 1.3.1 | 4 / 9 | |
| 1.3.0 | 4 / 9 | |
| 1.2.9 | 4 / 8 | |
| 1.2.8 | 4 / 8 | |
| 1.2.7 | 4 / 8 | |
| 1.2.6 | 4 / 8 | |
| 1.2.5 | 4 / 8 | |
| 1.2.4 | 3 / 9 | |
| 1.2.3 | 3 / 9 | |
| 1.2.2 | 3 / 9 | |
| 1.2.1 | 3 / 9 | |
| 1.2.0 | 3 / 9 | |
| 1.1.3 | 3 / 8 | |
| 1.1.2 | 3 / 8 | |
| 1.1.1 | 3 / 8 | |
| 1.1.0 | 3 / 8 | |
| 1.0.4 | 3 / 7 | |
| 1.0.3 | 3 / 5 | |
| 1.0.2 | 3 / 5 | |
| 1.0.1 | 3 / 5 | |
| 1.0.0 | 3 / 5 |
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.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.