@esome-dev/eaas-entity
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:@operato/shell | AI (phantom-deps): Sibling monorepo dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@operato/graphql | AI (phantom-deps): Sibling monorepo dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/dataset | AI (phantom-deps): Sibling monorepo dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/integration-base | AI (phantom-deps): Sibling monorepo dep referenced in config; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.2.121 | 6 / 0 | |
| 1.2.117 | 6 / 0 | |
| 1.2.115 | 6 / 0 | |
| 1.2.110 | 6 / 0 |
v1.2.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.