@intlayer/api
SDK for interacting with the Intlayer API, enabling content auditing, and managing organizations, projects, and users.
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): @intlayer/api is a scoped intlayer monorepo package; no relation to hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @intlayer/api is a scoped intlayer monorepo package; no relation to pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @intlayer/api is a scoped intlayer monorepo package; no relation to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @intlayer/api is a scoped intlayer monorepo package; no relation to ajv. | ai |
Versions (showing 51 of 136)
| Version | Deps | Published |
|---|---|---|
| 8.12.2 | 3 / 8 | |
| 8.12.1 | 3 / 8 | |
| 8.12.0 | 3 / 8 | |
| 8.11.3 | 3 / 8 | |
| 8.11.2 | 3 / 8 | |
| 8.11.1 | 3 / 8 | |
| 8.11.0 | 3 / 8 | |
| 8.10.1 | 3 / 8 | |
| 8.10.0 | 3 / 8 | |
| 8.9.8 | 3 / 8 | |
| 8.9.7 | 3 / 8 | |
| 8.9.6 | 3 / 8 | |
| 8.9.5 | 3 / 8 | |
| 8.9.4 | 3 / 8 | |
| 8.9.3 | 3 / 8 | |
| 8.9.2 | 3 / 8 | |
| 8.9.1 | 3 / 8 | |
| 8.9.0 | 3 / 8 | |
| 8.8.0 | 3 / 8 | |
| 8.7.14 | 3 / 8 | |
| 8.7.13 | 3 / 8 | |
| 8.7.12 | 3 / 8 | |
| 8.7.11 | 3 / 8 | |
| 8.7.10 | 3 / 8 | |
| 8.7.9 | 3 / 8 | |
| 8.7.8 | 3 / 8 | |
| 8.7.7 | 3 / 8 | |
| 8.7.6 | 3 / 8 | |
| 8.7.5 | 3 / 8 | |
| 8.7.4 | 3 / 8 | |
| 8.7.3 | 3 / 8 | |
| 8.7.2 | 3 / 8 | |
| 8.7.1 | 3 / 8 | |
| 8.7.0 | 3 / 8 | |
| 8.6.10 | 3 / 8 | |
| 8.6.9 | 3 / 8 | |
| 8.6.8 | 3 / 8 | |
| 8.6.7 | 3 / 8 | |
| 8.6.6 | 3 / 8 | |
| 8.6.5 | 3 / 8 | |
| 8.6.4 | 3 / 8 | |
| 8.6.3 | 3 / 8 | |
| 8.6.2 | 3 / 8 | |
| 8.6.1 | 3 / 8 | |
| 8.6.0 | 3 / 8 | |
| 8.5.2 | 3 / 8 | |
| 8.5.1 | 3 / 8 | |
| 8.5.0 | 3 / 8 | |
| 8.4.10 | 3 / 8 | |
| 8.4.9 | 3 / 8 | |
| 8.4.8 | 3 / 8 |
v8.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.1
2 findingsPackage name '@intlayer/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.
v8.10.0
2 findingsPackage name '@intlayer/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.
v8.9.8
2 findingsPackage name '@intlayer/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.
v8.9.7
2 findingsPackage name '@intlayer/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.
v8.9.6
2 findingsPackage name '@intlayer/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.
v8.9.5
2 findingsPackage name '@intlayer/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.
v8.9.4
2 findingsPackage name '@intlayer/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.
v8.9.3
2 findingsPackage name '@intlayer/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.
v8.9.2
2 findingsPackage name '@intlayer/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.
v8.9.1
2 findingsPackage name '@intlayer/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.
v8.9.0
2 findingsPackage name '@intlayer/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.
v8.8.0
2 findingsPackage name '@intlayer/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.
v8.7.14
2 findingsPackage name '@intlayer/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.
v8.7.13
2 findingsPackage name '@intlayer/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.
v8.7.12
2 findingsPackage name '@intlayer/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.
v8.7.10
2 findingsPackage name '@intlayer/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.
v8.7.9
2 findingsPackage name '@intlayer/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.
v8.7.8
2 findingsPackage name '@intlayer/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.
v8.7.7
2 findingsPackage name '@intlayer/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.
v8.7.5
2 findingsPackage name '@intlayer/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.
v8.7.4
2 findingsPackage name '@intlayer/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.
v8.7.3
2 findingsPackage name '@intlayer/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.
v8.7.2
2 findingsPackage name '@intlayer/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.
v8.7.1
2 findingsPackage name '@intlayer/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.
v8.7.0
2 findingsPackage name '@intlayer/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.
v8.6.10
2 findingsPackage name '@intlayer/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.
v8.6.9
2 findingsPackage name '@intlayer/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.
v8.6.8
2 findingsPackage name '@intlayer/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.
v8.6.7
2 findingsPackage name '@intlayer/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.
v8.6.6
2 findingsPackage name '@intlayer/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.
v8.6.5
2 findingsPackage name '@intlayer/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.
v8.6.4
2 findingsPackage name '@intlayer/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.
v8.6.3
2 findingsPackage name '@intlayer/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.
v8.6.2
2 findingsPackage name '@intlayer/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.
v8.6.1
2 findingsPackage name '@intlayer/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.
v8.6.0
2 findingsPackage name '@intlayer/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.
v8.5.2
2 findingsPackage name '@intlayer/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.
v8.5.1
2 findingsPackage name '@intlayer/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.
v8.5.0
2 findingsPackage name '@intlayer/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.
v8.4.10
2 findingsPackage name '@intlayer/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.
v8.4.9
2 findingsPackage name '@intlayer/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.
v8.4.8
2 findingsPackage name '@intlayer/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.