@tecsinapse/cortex-react
React components based in @tecsinapse/cortex-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tecsinapse/cortex-core | AI (dependencies): Same-org internal dependency; consistent across versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package from a known monorepo; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:react-imask | AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-spring | AI (phantom-deps): Declared runtime dep referenced in config; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 16 / 0 | |
| 2.4.0 | 16 / 0 | |
| 2.3.0 | 16 / 0 | |
| 2.2.2 | 16 / 0 | |
| 2.2.1 | 16 / 0 | |
| 2.2.0 | 16 / 0 | |
| 2.1.2 | 16 / 0 | |
| 2.1.1 | 16 / 0 | |
| 2.1.0 | 16 / 0 | |
| 2.0.1 | 14 / 0 | |
| 2.0.0 | 14 / 0 | |
| 1.15.6 | 14 / 0 | |
| 1.15.5 | 14 / 0 | |
| 1.15.4 | 14 / 0 | |
| 1.15.3 | 14 / 0 | |
| 1.15.2 | 14 / 0 | |
| 1.15.1 | 14 / 0 | |
| 1.15.0 | 14 / 0 | |
| 1.14.1 | 14 / 0 |
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.