@quenty/nevermore-template-helpers
Helpers to generate Nevermore package and game 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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Quenty's monorepo publishes many packages in rapid succession; pattern is consistent across 103 versions. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a well-known templating library; stable dependency for this template-helper package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): TypeScript build tool; chalk is a runtime dep used indirectly via compiled output. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): TypeScript build tool; execa is a runtime dep used indirectly via compiled output. | ai | |
| phantom-deps | phantom-dep:typescript-memoize | AI (phantom-deps): TypeScript build tool; typescript-memoize is a runtime dep used indirectly via compiled output. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm enforcer; stable pattern across this monorepo's packages, not arbitrary code. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 5 / 3 | |
| 1.14.0 | 5 / 3 | |
| 1.13.0 | 5 / 3 | |
| 1.12.0 | 5 / 3 | |
| 1.11.1 | 5 / 3 | |
| 1.11.0 | 5 / 3 | |
| 1.10.0 | 5 / 3 | |
| 1.9.0 | 5 / 3 | |
| 1.7.0 | 5 / 3 | |
| 1.6.2 | 5 / 3 | |
| 1.6.0 | 5 / 3 | |
| 1.5.0 | 5 / 3 | |
| 1.4.2 | 5 / 3 | |
| 1.4.1 | 5 / 3 | |
| 1.4.0 | 5 / 3 | |
| 1.3.0 | 5 / 3 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.