@things-factory/operato-gangsters
hatiolab groupware project
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all 1114 versions. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 (localhost) in a development config file — not a network exfiltration risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard migration file loader pattern iterating local filesystem paths; not arbitrary module loading. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.2.19 | 49 / 1 | |
| 9.2.16 | 49 / 1 | |
| 9.0.11 | 49 / 1 | |
| 8.0.74 | 48 / 1 | |
| 8.0.67 | 48 / 1 | |
| 8.0.63 | 48 / 1 |
v9.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.