@horizon-js/domain-schema-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pg | AI (phantom-deps): Database driver used in config/type generation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): Utility library used in config/type generation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): Type definitions loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@prisma/client | AI (phantom-deps): ORM framework loaded by convention; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Schema converter used in config/type generation; stable pattern for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 7 / 8 | |
| 1.6.2 | 7 / 8 | |
| 1.6.1 | 7 / 8 | |
| 1.6.0 | 7 / 8 | |
| 1.5.0 | 7 / 8 | |
| 1.4.2 | 7 / 8 |
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.1
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.