@lafken/api
Define AWS REST APIs using TypeScript decorators - declarative, type-safe infrastructure for API Gateway
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @lafken/api is a scoped AWS IaC package, not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @lafken/api is a scoped AWS IaC package, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @lafken/api is a scoped AWS IaC package, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @lafken/api is a scoped AWS IaC package, not a typosquat of ajv. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.12.14 | 2 / 12 | |
| 0.12.13 | 2 / 12 | |
| 0.12.12 | 2 / 12 | |
| 0.12.11 | 2 / 12 | |
| 0.12.10 | 2 / 12 | |
| 0.12.9 | 2 / 12 | |
| 0.12.8 | 2 / 12 | |
| 0.12.7 | 2 / 12 | |
| 0.12.6 | 2 / 12 | |
| 0.12.5 | 2 / 12 | |
| 0.12.4 | 2 / 12 | |
| 0.12.3 | 2 / 12 | |
| 0.12.2 | 2 / 12 | |
| 0.12.1 | 2 / 12 | |
| 0.12.0 | 2 / 12 | |
| 0.11.20 | 2 / 12 | |
| 0.11.19 | 2 / 12 | |
| 0.11.18 | 2 / 12 | |
| 0.11.17 | 2 / 12 | |
| 0.11.16 | 2 / 12 | |
| 0.11.15 | 2 / 12 | |
| 0.11.14 | 2 / 12 | |
| 0.11.13 | 2 / 12 | |
| 0.11.12 | 2 / 12 | |
| 0.11.11 | 2 / 12 | |
| 0.11.10 | 2 / 12 | |
| 0.11.9 | 2 / 12 | |
| 0.11.8 | 2 / 12 | |
| 0.11.7 | 2 / 12 | |
| 0.11.6 | 2 / 12 | |
| 0.11.5 | 2 / 12 | |
| 0.11.4 | 2 / 12 | |
| 0.11.3 | 2 / 12 | |
| 0.11.2 | 2 / 12 | |
| 0.11.1 | 2 / 12 | |
| 0.11.0 | 2 / 12 | |
| 0.10.6 | 2 / 12 | |
| 0.10.5 | 2 / 12 | |
| 0.10.4 | 2 / 12 | |
| 0.10.3 | 2 / 12 | |
| 0.10.2 | 2 / 12 | |
| 0.10.1 | 2 / 12 |
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.20
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.19
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.17
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.16
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.15
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.14
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.12
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.11
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.10
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
2 findingsPackage name '@lafken/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.