@raystack/frontier
A js library for frontier
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.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:react/dist/client.mjs | AI (source-diff): ESM counterpart of the same tsup bundle; same reasoning applies. | ai | |
| source-diff | obfuscated-file:react/dist/client.js | AI (source-diff): Standard tsup/esbuild bundle output; long lines are minified but not obfuscated. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:react/dist/client.mjs | AI (source-diff): Same as CJS counterpart; ESM bundle with identical benign patterns. | ai | |
| source-diff | net-exec-file:react/dist/client.js | AI (source-diff): Network calls are React/axios SDK usage; dynamic code execution is tsup __commonJS wrapper. No dropper pattern present. | ai | |
| phantom-deps | phantom-dep:@connectrpc/connect-query | AI (phantom-deps): Established library; config-referenced transitive dep is normal. | ai | |
| phantom-deps | phantom-dep:@raystack/proton | AI (phantom-deps): Same-org scoped dep; transitive usage in library is expected. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Established library; config-referenced transitive dep is normal. | ai | |
| phantom-deps | phantom-dep:@connectrpc/connect-web | AI (phantom-deps): Established library; config-referenced transitive dep is normal. | ai | |
| source-diff | net-exec-file:admin/dist/index.mjs | AI (source-diff): Same rationale as CJS counterpart; standard bundled UI code. | ai | |
| source-diff | obfuscated-file:admin/dist/index.js | AI (source-diff): Standard esbuild/tsup bundle output; long lines are minified but not obfuscated. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:admin/dist/index.js | AI (source-diff): Network calls and dynamic requires are part of the React UI bundle, not dropper behavior. | ai | |
| source-diff | obfuscated-file:admin/dist/index.mjs | AI (source-diff): Same tsup ESM bundle; long lines are minified output, not obfuscation. | ai | |
| dependencies | unvetted-dep:@raystack/proton | AI (dependencies): Internal org protobuf package pinned to a specific commit hash; consistent with @raystack ecosystem pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 231 versions in registry; publisher has 4 approved packages; dormancy likely reflects org release cadence, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established @raystack org package; provenance not used across their release history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @connectrpc/connect is a canonical Buf/ConnectRPC library, consistent with existing connect-query/connect-web deps already in the package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.103.2 | 20 / 29 | |
| 0.103.1 | 20 / 29 | |
| 0.102.0 | 20 / 29 | |
| 0.99.0 | 20 / 29 | |
| 0.96.0 | 20 / 29 | |
| 0.95.1 | 19 / 32 | |
| 0.95.0 | 19 / 32 | |
| 0.93.1 | 19 / 32 | |
| 0.92.1 | 19 / 32 | |
| 0.89.1 | 19 / 26 | |
| 0.81.0 | 19 / 27 | |
| 0.79.0 | 18 / 26 | |
| 0.78.2 | 18 / 26 | |
| 0.78.1 | 18 / 26 | |
| 0.78.0 | 18 / 26 | |
| 0.71.0 | 17 / 26 | |
| 0.70.1 | 13 / 26 | |
| 0.70.0 | 13 / 26 | |
| 0.69.0 | 13 / 26 | |
| 0.68.0 | 13 / 26 | |
| 0.67.0 | 13 / 26 | |
| 0.66.0 | 13 / 26 | |
| 0.65.0 | 13 / 26 | |
| 0.64.0 | 13 / 26 | |
| 0.63.0 | 15 / 26 | |
| 0.62.0 | 15 / 26 |
v0.103.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.103.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.102.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.