@apart-tech/intelligence-core
Core library: database, services, and providers for Apart Intelligence
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Standard prisma generate postinstall for Prisma client generation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): prisma is used in postinstall script and config files, not directly imported in JS — expected pattern. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod likely used for schema validation in config/type files; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.23.0 | 15 / 6 | |
| 1.19.0 | 8 / 3 | |
| 1.18.0 | 8 / 3 | |
| 1.17.0 | 8 / 3 | |
| 1.16.0 | 8 / 3 | |
| 0.1.0 | 4 / 4 |
v1.23.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aleksander-apart.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aleksander-apart.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aleksander-apart.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.