@getpara/react-sdk-lite
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sub-package of @getpara SDK suite; missing metadata is consistent across versions, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this SDK's sub-packages; not indicative of malicious intent. | ai | |
| phantom-deps | phantom-dep:zustand-sync-tabs | AI (phantom-deps): Declared in config but not directly imported; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/modal/utils/aaguiMetadata.js | AI (source-diff): File is a WebAuthn AAGUID metadata registry with base64 SVG icons — long lines are data, not obfuscation. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 14 / 26 | |
| 3.0.0 | 14 / 26 | |
| 2.32.1 | 12 / 22 | |
| 2.32.0 | 12 / 22 | |
| 2.31.0 | 12 / 22 | |
| 2.30.0 | 12 / 22 | |
| 2.29.0 | 12 / 22 | |
| 2.28.0 | 12 / 22 | |
| 2.27.0 | 12 / 22 | |
| 2.25.0 | 12 / 22 | |
| 2.24.0 | 12 / 22 | |
| 2.21.0 | 12 / 22 | |
| 2.12.0 | 10 / 12 | |
| 2.7.0 | 9 / 12 | |
| 2.2.0 | 9 / 12 | |
| 2.1.0 | 9 / 12 |
v3.1.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 (nsquare) than the most recent previously approved version (tbosch) on 2026-06-05, but nsquare 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.
v3.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tbosch) than the most recent previously approved version (nsquare) on 2026-05-28, but tbosch 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.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.