@contractspec/example.wealth-snapshot
Wealth Snapshot mini-app for accounts, assets, liabilities, and goals
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared in dependencies and used in schema validation; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.bus | AI (phantom-deps): Same-org scoped dependency declared and used; phantom-dep heuristic is a false positive for monorepo patterns. | ai | |
| source-diff | obfuscated-file:dist/node/ui/WealthSnapshotPreview.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/node/ui/index.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/node/ui/wealth-snapshot-preview.data.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/ui/WealthSnapshotPreview.js | AI (source-diff): Bun-bundled minified output (// @bun header); consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/ui/index.js | AI (source-diff): Bun-bundled minified output (// @bun header); consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/ui/wealth-snapshot-preview.data.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/browser/ui/WealthSnapshotPreview.js | AI (source-diff): Bun-bundled minified React component output; readable domain logic, no malicious payload. | ai | |
| source-diff | obfuscated-file:dist/browser/ui/index.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| source-diff | obfuscated-file:dist/browser/ui/wealth-snapshot-preview.data.js | AI (source-diff): Bun-bundled minified output; consistent with build toolchain. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.identity-rbac | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not reliable for bundled/re-exported modules. | ai | |
| phantom-deps | phantom-dep:@contractspec/module.audit-trail | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not reliable for bundled/re-exported modules. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom declared as peer/runtime dep in a React UI package; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.notification | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not reliable for bundled/re-exported modules. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.design-system | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic not reliable for bundled/re-exported modules. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 3.8.5 | 8 / 5 | |
| 3.8.4 | 8 / 5 | |
| 3.8.3 | 8 / 5 | |
| 3.8.2 | 8 / 5 | |
| 3.8.1 | 8 / 5 | |
| 3.8.0 | 8 / 5 | |
| 3.7.25 | 5 / 3 | |
| 3.7.24 | 5 / 3 | |
| 3.7.23 | 5 / 3 | |
| 3.7.22 | 5 / 3 | |
| 3.7.21 | 5 / 3 | |
| 3.7.20 | 5 / 3 | |
| 3.7.19 | 5 / 3 | |
| 3.7.18 | 5 / 3 | |
| 3.7.17 | 5 / 3 | |
| 3.7.16 | 5 / 3 | |
| 3.7.15 | 5 / 3 | |
| 3.7.14 | 5 / 3 | |
| 3.7.12 | 5 / 3 | |
| 3.7.10 | 5 / 3 | |
| 3.7.7 | 5 / 3 | |
| 3.7.6 | 5 / 3 | |
| 3.7.5 | 5 / 3 | |
| 3.7.4 | 5 / 3 | |
| 3.7.3 | 5 / 3 | |
| 3.7.1 | 5 / 3 | |
| 3.7.0 | 5 / 3 | |
| 3.6.0 | 5 / 3 | |
| 3.5.5 | 5 / 3 | |
| 3.5.4 | 5 / 3 | |
| 3.5.3 | 5 / 3 | |
| 3.5.2 | 5 / 3 | |
| 3.5.0 | 5 / 3 | |
| 3.4.3 | 5 / 3 | |
| 3.4.2 | 5 / 3 | |
| 3.4.1 | 5 / 3 | |
| 3.4.0 | 5 / 3 | |
| 3.3.0 | 5 / 3 | |
| 3.2.0 | 5 / 3 | |
| 3.1.1 | 5 / 3 | |
| 3.0.0 | 5 / 3 | |
| 2.9.1 | 5 / 3 | |
| 2.9.0 | 5 / 3 | |
| 2.8.0 | 5 / 3 | |
| 2.7.0 | 5 / 3 | |
| 2.6.0 | 5 / 3 | |
| 2.5.0 | 5 / 3 | |
| 2.4.0 | 5 / 3 | |
| 2.3.0 | 5 / 3 | |
| 2.2.0 | 5 / 3 | |
| 2.1.1 | 5 / 3 | |
| 2.1.0 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.62.0 | 5 / 3 | |
| 1.61.0 | 5 / 3 | |
| 1.60.0 | 5 / 3 | |
| 1.59.0 | 5 / 3 | |
| 1.58.0 | 5 / 3 | |
| 1.57.0 | 5 / 3 | |
| 1.56.1 | 5 / 3 | |
| 1.56.0 | 5 / 3 | |
| 1.55.0 | 5 / 3 | |
| 1.54.0 | 5 / 3 | |
| 1.53.0 | 5 / 3 | |
| 1.52.0 | 5 / 3 | |
| 1.51.0 | 5 / 3 | |
| 1.50.0 | 5 / 3 | |
| 1.49.0 | 5 / 3 | |
| 1.48.1 | 5 / 3 | |
| 1.48.0 | 5 / 3 | |
| 1.47.0 | 5 / 3 | |
| 1.46.2 | 5 / 3 | |
| 1.46.1 | 5 / 3 | |
| 1.46.0 | 5 / 3 | |
| 1.45.6 | 5 / 3 | |
| 1.45.5 | 5 / 3 | |
| 1.45.4 | 5 / 3 | |
| 1.45.3 | 5 / 3 | |
| 1.45.2 | 5 / 3 | |
| 1.45.1 | 7 / 3 | |
| 1.45.0 | 7 / 3 | |
| 1.44.1 | 7 / 3 | |
| 1.44.0 | 7 / 3 |
v3.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
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.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.