@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, so a manually published version cannot be tied back to a reviewed commit.
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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.2.123 | 6 / 0 | |
| 1.2.121 | 6 / 0 | |
| 1.2.117 | 6 / 0 | |
| 1.2.115 | 6 / 0 | |
| 1.2.110 | 6 / 0 | |
| 1.2.22 | 6 / 0 | |
| 1.2.21 | 6 / 0 | |
| 1.2.20 | 6 / 0 | |
| 1.2.19 | 6 / 0 | |
| 1.2.18 | 6 / 0 | |
| 1.2.17 | 6 / 0 | |
| 1.2.16 | 6 / 0 | |
| 1.2.15 | 6 / 0 | |
| 1.2.14 | 6 / 0 | |
| 1.2.13 | 6 / 0 | |
| 1.2.12 | 6 / 0 | |
| 1.2.11 | 6 / 0 | |
| 1.2.10 | 6 / 0 | |
| 1.2.9 | 6 / 0 | |
| 1.2.8 | 6 / 0 | |
| 1.2.7 | 6 / 0 | |
| 1.2.6 | 6 / 0 | |
| 1.2.5 | 6 / 0 | |
| 1.1.9 | 6 / 0 | |
| 1.1.8 | 6 / 0 | |
| 1.1.7 | 6 / 0 | |
| 1.1.6 | 6 / 0 | |
| 1.1.5 | 6 / 0 | |
| 1.1.4 | 6 / 0 | |
| 1.1.3 | 6 / 0 | |
| 1.1.2 | 6 / 0 |
v1.2.123
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cloud9316) than the most recent previously approved version (nalshya113) on 2026-07-03, but cloud9316 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.