@esome-dev/failure
module for handling inverter troubleshooting
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/dataset | AI (phantom-deps): Config-file-only reference in a things-factory ecosystem module; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/shell | AI (phantom-deps): Config-file-only reference in a things-factory ecosystem module; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.121 | 3 / 0 | |
| 1.2.119 | 3 / 0 | |
| 1.2.118 | 3 / 0 | |
| 1.2.117 | 3 / 0 | |
| 1.2.109 | 3 / 0 | |
| 1.2.96 | 3 / 0 |
v1.2.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.118
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.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.