← Home

@privateaim/core-kit

npm

[![npm version][npm-src]][npm-href]

46
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

tada5hi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 46 of 46)

Version Deps Published
0.11.0 5 / 3
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
0.8.12 0 / 2
0.8.11 0 / 2
0.8.10 0 / 2
0.8.9 0 / 2
0.8.8 0 / 2
0.8.7 0 / 2
0.8.6 0 / 2
0.8.5 0 / 2
0.8.4 0 / 2
0.8.3 0 / 2
0.8.2 0 / 2
0.8.1 0 / 2
0.8.0 0 / 2
0.7.0 0 / 2
0.6.0 0 / 2

v0.8.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.