@contractspec/app.registry-server
Website: https://contractspec.io
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped package with repo URL; missing description is cosmetic, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a disqualifier for established packages. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.contracts | AI (phantom-deps): Same-org internal dependency; expected pattern for monorepo packages. | ai | |
| dependencies | unvetted-dep:@elysiajs/server-timing | AI (dependencies): Legitimate Elysia framework plugin; stable dependency for this package across versions. | ai | |
| phantom-deps | phantom-dep:elysia | AI (phantom-deps): Elysia is a framework likely used via config/type imports; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.contracts-spec | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@elysiajs/cors | AI (phantom-deps): Elysia plugin referenced in config; stable false positive for this monorepo app package. | ai | |
| phantom-deps | phantom-dep:@elysiajs/server-timing | AI (phantom-deps): Elysia plugin referenced in config; stable false positive for this monorepo app package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.logger | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.7.29 | 5 / 0 | |
| 3.7.27 | 5 / 0 | |
| 3.7.5 | 5 / 0 | |
| 3.6.0 | 5 / 0 | |
| 3.5.5 | 5 / 0 | |
| 3.4.3 | 5 / 0 | |
| 2.9.1 | 5 / 0 | |
| 2.9.0 | 5 / 0 | |
| 2.0.0 | 5 / 0 | |
| 1.51.0 | 5 / 0 | |
| 1.47.0 | 5 / 0 | |
| 1.45.5 | 5 / 0 | |
| 1.45.2 | 5 / 0 | |
| 1.45.1 | 5 / 0 | |
| 1.45.0 | 5 / 0 | |
| 1.44.1 | 5 / 0 |
v3.7.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.