@moneybutton/postmessage-client
Money Button PostMessage client.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from calvo.generico to ryanxcharles occurred in 2019 and is a documented legitimate transition. ryanxcharles (Ryan X. Charles) is the known founder of Money Button with a strong track record. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a framework-scoped package loaded by convention via Babel transform; not a security concern. | ai | |
| phantom-deps | phantom-dep:@moneybutton/config | AI (phantom-deps): Same-org scoped package in a monorepo setup; benign phantom dep pattern. | ai | |
| phantom-deps | phantom-dep:@moneybutton/logger | AI (phantom-deps): Same-org scoped package in a monorepo setup; benign phantom dep pattern. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.38.10 | 1 / 20 | |
| 0.38.8 | 3 / 25 | |
| 0.38.7 | 3 / 25 | |
| 0.38.6 | 3 / 25 | |
| 0.38.5 | 3 / 25 | |
| 0.38.4 | 3 / 25 | |
| 0.38.3 | 3 / 25 | |
| 0.38.2 | 3 / 25 | |
| 0.38.1 | 3 / 25 | |
| 0.37.0 | 3 / 25 | |
| 0.36.0 | 3 / 25 | |
| 0.35.0 | 3 / 25 | |
| 0.34.0 | 3 / 25 | |
| 0.33.0 | 3 / 25 | |
| 0.32.0 | 3 / 27 | |
| 0.31.3 | 3 / 27 | |
| 0.31.2 | 3 / 27 | |
| 0.31.1 | 3 / 27 | |
| 0.31.0 | 3 / 27 | |
| 0.30.1 | 3 / 27 | |
| 0.30.0 | 3 / 27 | |
| 0.28.1 | 3 / 27 | |
| 0.28.0 | 3 / 27 | |
| 0.27.0 | 3 / 27 | |
| 0.26.0 | 3 / 27 | |
| 0.25.0 | 3 / 27 | |
| 0.24.4 | 3 / 27 | |
| 0.24.3 | 3 / 27 | |
| 0.24.2 | 3 / 27 | |
| 0.24.0 | 3 / 27 | |
| 0.23.1 | 3 / 27 | |
| 0.23.0 | 3 / 27 | |
| 0.22.2 | 3 / 27 | |
| 0.21.11 | 3 / 27 | |
| 0.21.9 | 3 / 27 | |
| 0.21.8 | 3 / 27 | |
| 0.21.7 | 3 / 27 | |
| 0.21.5 | 3 / 27 | |
| 0.21.2 | 3 / 27 | |
| 0.21.1 | 3 / 27 |
v0.38.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-07-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.38.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.38.1
2 findingsThis version was published by a different npm account than previous versions on 2020-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
2 findingsThis version was published by a different npm account than previous versions on 2020-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
2 findingsThis version was published by a different npm account than previous versions on 2020-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
2 findingsThis version was published by a different npm account than previous versions on 2019-11-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
2 findingsThis version was published by a different npm account than previous versions on 2019-11-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.24.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.21.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.21.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.21.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.