@karmaniverous/jeeves-meta
Fastify HTTP service for the Jeeves Meta synthesis engine
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a well-known templating library; its use here is consistent with a Fastify service package. | ai | |
| phantom-deps | phantom-dep:@karmaniverous/jeeves | AI (phantom-deps): Same-org peer dependency; likely consumed indirectly or via CLI entrypoint, not a direct import. | ai | |
| phantom-deps | phantom-dep:package-directory | AI (phantom-deps): package-directory is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.15.8 | 9 / 13 | |
| 0.15.5 | 9 / 13 | |
| 0.15.4 | 8 / 17 | |
| 0.15.2 | 8 / 17 | |
| 0.15.1 | 8 / 17 | |
| 0.13.9 | 8 / 17 | |
| 0.13.5 | 8 / 17 | |
| 0.13.1 | 8 / 17 | |
| 0.13.0 | 8 / 17 | |
| 0.12.2 | 8 / 17 | |
| 0.12.0 | 8 / 17 | |
| 0.11.3 | 8 / 16 | |
| 0.11.2 | 8 / 16 | |
| 0.10.0 | 7 / 15 | |
| 0.9.0 | 7 / 15 | |
| 0.8.0 | 7 / 15 | |
| 0.7.0 | 7 / 15 | |
| 0.6.1 | 6 / 15 | |
| 0.6.0 | 6 / 15 | |
| 0.5.0 | 6 / 12 | |
| 0.4.2 | 5 / 12 | |
| 0.4.1 | 5 / 12 | |
| 0.4.0 | 5 / 12 | |
| 0.3.3 | 1 / 15 | |
| 0.3.2 | 1 / 15 | |
| 0.3.1 | 1 / 15 | |
| 0.3.0 | 1 / 15 | |
| 0.2.2 | 1 / 15 | |
| 0.2.1 | 1 / 15 | |
| 0.2.0 | 1 / 15 | |
| 0.1.0 | 1 / 15 |
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.