@twinfinity/templates
CLI for scaffolding Twinfinity starter projects
3
Versions
ISC
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
sejjzj
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Template scaffold package; no provenance is low risk given clean content and no install scripts. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a project template scaffold; missing metadata fields are expected for this artifact type. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Template scaffold package; no description is expected by design. | ai | |
| phantom-deps | phantom-dep:@types/inquirer | AI (phantom-deps): Type-only declaration package; not directly imported by design in template scaffolds. | ai |
v6.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.