@lindorm/iris
Decorator-driven messaging for Node.js with a single API across multiple brokers. Define messages once, publish and subscribe against memory, RabbitMQ, Kafka, NATS, or Redis Streams.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of a multi-package monorepo; sparse README/metadata is typical for internal utility packages in this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @lindorm/* packages; not indicative of malicious intent. | ai | |
| dependencies | unvetted-dep:@lindorm/errors | AI (dependencies): Same monorepo/publisher; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@lindorm/is | AI (dependencies): Same monorepo/publisher; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@lindorm/json-kit | AI (dependencies): Same monorepo/publisher; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@lindorm/scanner | AI (dependencies): Same monorepo/publisher; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@lindorm/aes | AI (dependencies): Same monorepo/publisher; stable false positive for this package family. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 11 / 8 | |
| 0.4.2 | 11 / 8 | |
| 0.4.0 | 11 / 8 | |
| 0.1.1 | 10 / 7 | |
| 0.1.0 | 10 / 7 |
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.