@lindorm/hermes
A decorator-driven CQRS and Event Sourcing framework for TypeScript, with pluggable persistence and messaging supplied by `@lindorm/proteus` and `@lindorm/iris`.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lindorm/postgres | AI (dependencies): Same-org sibling package from lindorm-io monorepo. | ai | |
| dependencies | unvetted-dep:@lindorm/mongo | AI (dependencies): Same-org sibling package from lindorm-io monorepo; consistent pattern across all @lindorm/* deps. | ai | |
| dependencies | unvetted-dep:@lindorm/redis | AI (dependencies): Same-org sibling package from lindorm-io monorepo. | ai | |
| dependencies | unvetted-dep:@lindorm/rabbit | AI (dependencies): Same-org sibling package from lindorm-io monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @lindorm/* packages; no CI provenance is a stable characteristic of this monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @lindorm/types, an internal monorepo package consistent with the existing @lindorm/* dependency set. | ai | |
| phantom-deps | phantom-dep:@lindorm/random | AI (phantom-deps): Same-org dependency; likely used transitively or in non-imported paths within the monorepo. | ai | |
| typosquat | typosquat.levenshtein:helmet | AI (typosquat): Scoped @lindorm package in established monorepo; Levenshtein match to 'helmet' is coincidental. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 16 / 3 | |
| 0.7.2 | 16 / 3 | |
| 0.7.1 | 16 / 3 | |
| 0.7.0 | 16 / 3 | |
| 0.6.1 | 15 / 3 | |
| 0.6.0 | 15 / 3 | |
| 0.5.0 | 13 / 3 | |
| 0.3.7 | 12 / 6 | |
| 0.3.6 | 12 / 6 | |
| 0.3.5 | 12 / 6 | |
| 0.3.4 | 12 / 6 | |
| 0.3.3 | 12 / 6 | |
| 0.3.2 | 12 / 7 | |
| 0.2.3 | 15 / 2 | |
| 0.2.2 | 15 / 2 | |
| 0.2.1 | 15 / 2 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
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.2.3
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.2.2
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.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.