@privateaim/messenger-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@validup/zod | AI (dependencies): Direct replacement for @validup/adapter-zod from the same validup ecosystem; low-risk refactor. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal library under @privateaim org; missing metadata is a style issue, not a spam/malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Package consistently published without provenance; low-risk ecosystem package. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.11.2 | 3 / 2 | |
| 0.11.1 | 3 / 2 | |
| 0.11.0 | 3 / 2 | |
| 0.10.3 | 3 / 2 | |
| 0.10.2 | 3 / 2 | |
| 0.10.1 | 3 / 2 | |
| 0.10.0 | 3 / 2 | |
| 0.7.46 | 3 / 2 | |
| 0.7.44 | 3 / 2 | |
| 0.7.43 | 3 / 2 | |
| 0.7.42 | 3 / 2 | |
| 0.7.40 | 3 / 2 | |
| 0.7.39 | 3 / 2 | |
| 0.7.38 | 3 / 2 | |
| 0.7.37 | 3 / 2 | |
| 0.7.35 | 3 / 2 | |
| 0.7.34 | 3 / 2 | |
| 0.7.33 | 3 / 2 | |
| 0.7.32 | 3 / 2 | |
| 0.7.31 | 3 / 2 | |
| 0.7.30 | 3 / 2 | |
| 0.7.29 | 3 / 2 | |
| 0.7.28 | 3 / 2 | |
| 0.7.27 | 3 / 2 | |
| 0.7.26 | 3 / 2 | |
| 0.7.24 | 3 / 2 | |
| 0.7.23 | 3 / 2 | |
| 0.7.22 | 3 / 1 | |
| 0.7.21 | 3 / 1 | |
| 0.7.20 | 3 / 1 | |
| 0.7.19 | 3 / 1 | |
| 0.7.18 | 3 / 1 | |
| 0.7.17 | 3 / 1 | |
| 0.7.16 | 3 / 1 | |
| 0.7.15 | 3 / 1 | |
| 0.7.14 | 3 / 1 | |
| 0.7.13 | 3 / 1 | |
| 0.7.12 | 3 / 1 | |
| 0.7.11 | 3 / 1 | |
| 0.7.10 | 3 / 1 | |
| 0.7.9 | 3 / 1 | |
| 0.7.8 | 3 / 1 | |
| 0.7.7 | 3 / 1 | |
| 0.7.6 | 0 / 1 | |
| 0.7.5 | 0 / 1 | |
| 0.7.4 | 0 / 1 | |
| 0.7.3 | 0 / 1 | |
| 0.7.2 | 0 / 1 | |
| 0.7.1 | 0 / 1 | |
| 0.7.0 | 0 / 1 | |
| 0.6.0 | 0 / 1 |
v0.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.