@things-factory/api
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped monorepo package; edit-distance match to 'hapi' is coincidental, not a squatting attempt. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped monorepo package; edit-distance match to 'pg' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped monorepo package; edit-distance match to 'joi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped monorepo package; edit-distance match to 'ajv' is coincidental. | ai | |
| phantom-deps | phantom-dep:swagger-jsdoc | AI (phantom-deps): swagger-jsdoc is a declared runtime dep used via config/runtime loading, not direct import; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 6 / 0 | |
| 9.2.19 | 6 / 0 | |
| 9.0.20 | 6 / 0 | |
| 9.0.0 | 6 / 0 | |
| 8.0.87 | 6 / 0 | |
| 8.0.63 | 6 / 0 | |
| 4.3.689 | 6 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.87
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.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.