@privateaim/core-kit
[![npm version][npm-src]][npm-href]
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @authup/core-kit is from the same ecosystem/author; addition is contextually appropriate for this package. | ai | |
| dependencies | unvetted-dep:@privateaim/errors | AI (dependencies): Same-org package (@privateaim namespace); routine internal dependency, stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with sparse metadata; pattern is stable across all @privateaim/* releases. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is a consistent pattern across this org's packages, not a malware signal. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 5 / 3 | |
| 0.10.0 | 4 / 3 | |
| 0.8.43 | 4 / 3 | |
| 0.8.42 | 4 / 3 | |
| 0.8.41 | 4 / 3 | |
| 0.8.39 | 0 / 3 | |
| 0.8.38 | 0 / 3 | |
| 0.8.37 | 0 / 3 | |
| 0.8.36 | 0 / 3 | |
| 0.8.34 | 0 / 3 | |
| 0.8.33 | 0 / 3 | |
| 0.8.32 | 0 / 3 | |
| 0.8.31 | 0 / 3 | |
| 0.8.30 | 0 / 3 | |
| 0.8.29 | 0 / 3 | |
| 0.8.28 | 0 / 3 | |
| 0.8.27 | 0 / 3 | |
| 0.8.26 | 0 / 3 | |
| 0.8.25 | 0 / 3 | |
| 0.8.23 | 0 / 3 | |
| 0.8.22 | 0 / 3 | |
| 0.8.21 | 0 / 3 | |
| 0.8.20 | 0 / 3 | |
| 0.8.19 | 0 / 3 | |
| 0.8.18 | 0 / 3 | |
| 0.8.17 | 0 / 3 | |
| 0.8.16 | 0 / 3 | |
| 0.8.15 | 0 / 2 | |
| 0.8.14 | 0 / 2 | |
| 0.8.13 | 0 / 2 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.