@asgardeo/react
React implementation of Asgardeo JavaScript SDK.
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@wso2/eslint-plugin | AI (npm-metadata): devDependency only; internal WSO2 linting config, not included in published dist. | ai | |
| npm-metadata | url-dep:@wso2/prettier-config | AI (npm-metadata): devDependency only; internal WSO2 prettier config, not included in published dist. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is the build tool used in esbuild.config.mjs; declared as dep for bundler use, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as dep, implicitly used by compiled output. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a legitimate runtime dep for a React SDK; referenced in config/build files. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only dep for a React package; framework-scoped, loaded by convention. | ai |
Versions (showing 27 of 129)
| Version | Deps | Published |
|---|---|---|
| 0.5.24 | 7 / 15 | |
| 0.5.23 | 7 / 15 | |
| 0.5.22 | 7 / 15 | |
| 0.5.21 | 7 / 15 | |
| 0.5.20 | 7 / 15 | |
| 0.5.19 | 7 / 15 | |
| 0.5.18 | 7 / 15 | |
| 0.5.17 | 7 / 15 | |
| 0.5.16 | 7 / 15 | |
| 0.5.15 | 7 / 15 | |
| 0.5.14 | 7 / 15 | |
| 0.5.13 | 7 / 15 | |
| 0.5.12 | 7 / 15 | |
| 0.5.11 | 7 / 15 | |
| 0.5.10 | 7 / 15 | |
| 0.5.9 | 7 / 15 | |
| 0.5.8 | 7 / 15 | |
| 0.5.7 | 7 / 15 | |
| 0.5.6 | 7 / 15 | |
| 0.5.5 | 7 / 15 | |
| 0.5.4 | 7 / 15 | |
| 0.5.3 | 7 / 15 | |
| 0.5.2 | 7 / 15 | |
| 0.5.1 | 7 / 15 | |
| 0.5.0 | 7 / 15 | |
| 0.4.0 | 7 / 15 | |
| 0.3.0 | 6 / 15 |
v0.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.