@nmtjs/msgpack-format
MessagePack serialization format for the Neemata protocol.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nmtjs/common | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on peer/dep dual-declaration pattern, not a real concern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 3 / 0 | |
| 0.15.2 | 3 / 0 | |
| 0.15.1 | 3 / 0 | |
| 0.15.0 | 3 / 0 |
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.