@intentweave/server-core
IntentWeave server foundation — Fastify, Neo4j pool, session/workspace middleware, plugin system
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Transitive via fastify-type-provider-zod; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@intentweave/core | AI (phantom-deps): Same-org peer dependency; intentional scoped pattern. | ai | |
| phantom-deps | phantom-dep:fastify-type-provider-zod | AI (phantom-deps): Used via config/plugin system; stable for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 10 / 3 | |
| 0.13.0 | 10 / 3 | |
| 0.12.0 | 10 / 3 | |
| 0.11.1 | 10 / 3 | |
| 0.11.0 | 10 / 3 | |
| 0.10.0 | 10 / 3 | |
| 0.9.0 | 10 / 3 | |
| 0.8.0 | 10 / 3 | |
| 0.7.0 | 10 / 3 | |
| 0.6.0 | 10 / 3 | |
| 0.5.0 | 10 / 3 | |
| 0.4.0 | 10 / 3 | |
| 0.1.0 | 10 / 3 |
v0.15.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.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.