@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, so a manually published version cannot be tied back to a reviewed commit.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@raystack/apsara-v1 | AI (dependencies): Same-org sibling package (Raystack's own apsara UI lib), aliased as pre-release. | ai | |
| source-diff | obfuscated-file:api-client/dist/index.d.ts | AI (source-diff): Generated API client type definitions; long lines are from codegen, not obfuscation. | 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 | |
| source-diff | obfuscated-file:react/dist/client.mjs | AI (source-diff): ESM counterpart of the same tsup bundle; same reasoning applies. | 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 | |
| phantom-deps | phantom-dep:@connectrpc/connect-query | AI (phantom-deps): Established library; config-referenced transitive dep is normal. | 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.mjs | AI (source-diff): Same rationale as CJS counterpart; standard bundled UI code. | ai | |
| source-diff | obfuscated-file:admin/dist/index.mjs | AI (source-diff): Same tsup ESM bundle; long lines are minified output, not obfuscation. | 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 | |
| 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 | |
| dependencies | unvetted-dep:@raystack/proton | AI (dependencies): Internal org protobuf package pinned to a specific commit hash; consistent with @raystack ecosystem pattern. | 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 83 of 183)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 14 / 24 | |
| 0.16.1 | 14 / 24 | |
| 0.16.0 | 14 / 24 | |
| 0.15.0 | 14 / 24 | |
| 0.14.0 | 14 / 24 | |
| 0.13.0 | 14 / 24 | |
| 0.12.0 | 14 / 24 | |
| 0.11.3 | 14 / 24 | |
| 0.11.2 | 14 / 24 | |
| 0.11.1 | 14 / 24 | |
| 0.11.0 | 14 / 24 | |
| 0.10.0 | 14 / 24 | |
| 0.9.3 | 14 / 24 | |
| 0.9.2 | 14 / 24 | |
| 0.9.1 | 14 / 24 | |
| 0.9.0 | 14 / 24 | |
| 0.8.42 | 14 / 24 | |
| 0.8.41 | 14 / 24 | |
| 0.8.40 | 14 / 24 | |
| 0.8.39 | 14 / 24 | |
| 0.8.38 | 14 / 24 | |
| 0.8.37 | 14 / 24 | |
| 0.8.36 | 14 / 24 | |
| 0.8.35 | 14 / 24 | |
| 0.8.34 | 14 / 24 | |
| 0.8.33 | 14 / 24 | |
| 0.8.32 | 14 / 24 | |
| 0.8.31 | 14 / 24 | |
| 0.8.30 | 14 / 24 | |
| 0.8.29 | 14 / 24 | |
| 0.8.28 | 14 / 24 | |
| 0.8.27 | 14 / 24 | |
| 0.8.26 | 14 / 24 | |
| 0.8.25 | 14 / 24 | |
| 0.8.24 | 14 / 24 | |
| 0.8.23 | 14 / 24 | |
| 0.8.22 | 14 / 24 | |
| 0.8.21 | 14 / 24 | |
| 0.8.20 | 14 / 24 | |
| 0.8.19 | 14 / 24 | |
| 0.8.18 | 14 / 24 | |
| 0.8.17 | 14 / 24 | |
| 0.8.15 | 12 / 19 | |
| 0.8.14 | 12 / 19 | |
| 0.8.11 | 11 / 18 | |
| 0.8.10 | 11 / 18 | |
| 0.8.9 | 11 / 18 | |
| 0.8.8 | 11 / 18 | |
| 0.8.7 | 11 / 18 | |
| 0.8.6 | 11 / 18 | |
| 0.8.5 | 11 / 18 | |
| 0.8.4 | 11 / 18 | |
| 0.8.3 | 11 / 18 | |
| 0.8.2 | 11 / 18 | |
| 0.8.1 | 11 / 18 | |
| 0.8.0 | 10 / 18 | |
| 0.7.24 | 10 / 18 | |
| 0.7.23 | 10 / 18 | |
| 0.7.22 | 10 / 18 | |
| 0.7.21 | 10 / 18 | |
| 0.7.20 | 10 / 18 | |
| 0.7.19 | 10 / 18 | |
| 0.7.18 | 10 / 18 | |
| 0.7.17 | 9 / 18 | |
| 0.7.16 | 9 / 18 | |
| 0.7.15 | 9 / 18 | |
| 0.7.14 | 9 / 18 | |
| 0.7.13 | 9 / 18 | |
| 0.7.12 | 9 / 18 | |
| 0.7.8 | 9 / 18 | |
| 0.7.7 | 9 / 25 | |
| 0.0.12 | 9 / 17 | |
| 0.0.11 | 9 / 17 | |
| 0.0.10 | 9 / 17 | |
| 0.0.9 | 9 / 17 | |
| 0.0.8 | 9 / 17 | |
| 0.0.7 | 9 / 17 | |
| 0.0.6 | 9 / 17 | |
| 0.0.5 | 8 / 17 | |
| 0.0.4 | 7 / 16 | |
| 0.0.3 | 7 / 16 | |
| 0.0.2 | 5 / 13 | |
| 0.0.1 | 5 / 13 |
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
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.9.1
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.9.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.8.42
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.8.41
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.8.40
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.8.39
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.8.38
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.8.37
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.8.36
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.8.35
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.8.34
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.8.33
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.8.32
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.8.31
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.8.30
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.8.29
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.8.28
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.8.27
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.8.26
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.8.25
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.8.24
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.8.23
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.8.22
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.8.21
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.8.20
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.8.19
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.8.18
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.8.17
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.8.15
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.8.14
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.8.11
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.8.10
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.8.9
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.8.8
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.8.7
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.8.6
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.8.5
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.8.4
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.8.3
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.8.2
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.8.1
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.8.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.7.24
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.7.23
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.7.22
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.7.21
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.7.20
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.7.19
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.7.18
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.7.17
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.7.16
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.7.15
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.7.14
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.7.13
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.7.12
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.7.8
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.7.7
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.0.12
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.0.11
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.0.10
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.0.9
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.0.8
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.0.7
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.0.6
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.0.5
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.0.4
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.0.3
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.0.2
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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.