@inlang/sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() appears in a test file mocking fs.promises — not production obfuscation. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.10.2 | 5 / 10 | |
| 2.10.1 | 5 / 10 | |
| 2.10.0 | 5 / 10 | |
| 2.9.3 | 5 / 10 | |
| 2.9.2 | 5 / 10 | |
| 2.9.1 | 5 / 10 | |
| 2.9.0 | 5 / 10 | |
| 2.8.0 | 5 / 10 | |
| 2.7.0 | 5 / 10 | |
| 2.6.2 | 5 / 10 | |
| 2.6.1 | 5 / 10 | |
| 2.6.0 | 5 / 10 | |
| 2.5.0 | 5 / 10 | |
| 2.4.10 | 5 / 11 | |
| 2.4.9 | 5 / 11 | |
| 2.4.8 | 5 / 11 | |
| 2.4.7 | 5 / 11 | |
| 2.4.6 | 5 / 11 | |
| 2.4.5 | 5 / 11 | |
| 2.4.4 | 5 / 11 | |
| 2.4.3 | 5 / 11 | |
| 2.4.2 | 5 / 11 | |
| 2.4.1 | 5 / 11 | |
| 2.4.0 | 5 / 11 | |
| 2.3.0 | 5 / 11 | |
| 2.2.2 | 5 / 10 | |
| 2.2.1 | 5 / 10 | |
| 2.2.0 | 5 / 10 | |
| 2.1.3 | 6 / 11 | |
| 2.1.2 | 6 / 11 | |
| 2.1.1 | 6 / 11 | |
| 2.1.0 | 6 / 11 | |
| 2.0.1 | 6 / 11 | |
| 2.0.0 | 6 / 11 |
v2.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-02-17, but inlangbot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-02-10, but inlangbot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (inlangbot) than the most recent previously approved version (samuelstroschein) on 2025-01-23, but inlangbot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (samuelstroschein) than the most recent previously approved version (inlangbot) on 2025-01-17, but samuelstroschein is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.