@reactionary/core
This library was generated with [Nx](https://nx.dev).
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual to GitHub Actions CI/CD with SLSA attestation; provenance direction is IMPROVED, not a risk signal. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @reactionary/core vs unscoped cors — edit-distance match is a false positive; different namespace and purpose. | ai | |
| phantom-deps | phantom-dep:vitest | AI (phantom-deps): vitest is listed as a runtime dep but is a dev/test tool; phantom-dep heuristic fires correctly but is a package quality issue, not a security one. | ai | |
| phantom-deps | phantom-dep:@nx/vite | AI (phantom-deps): @nx/vite is a build tool incorrectly listed as runtime dep; same false-positive pattern as vitest. | ai |
Versions (showing 100 of 143)
| Version | Deps | Published |
|---|---|---|
| 0.9.39 | 4 / 2 | |
| 0.9.38 | 4 / 2 | |
| 0.9.37 | 4 / 2 | |
| 0.9.28 | 4 / 2 | |
| 0.9.27 | 4 / 2 | |
| 0.9.26 | 4 / 2 | |
| 0.9.25 | 4 / 2 | |
| 0.9.24 | 4 / 2 | |
| 0.9.23 | 4 / 2 | |
| 0.9.22 | 4 / 2 | |
| 0.9.21 | 4 / 2 | |
| 0.9.20 | 4 / 2 | |
| 0.9.19 | 4 / 2 | |
| 0.9.18 | 4 / 2 | |
| 0.9.17 | 4 / 2 | |
| 0.9.16 | 4 / 2 | |
| 0.9.15 | 4 / 2 | |
| 0.9.14 | 4 / 2 | |
| 0.9.13 | 4 / 2 | |
| 0.9.12 | 4 / 2 | |
| 0.9.11 | 4 / 2 | |
| 0.9.8 | 6 / 0 | |
| 0.9.7 | 6 / 0 | |
| 0.9.6 | 6 / 0 | |
| 0.9.5 | 6 / 0 | |
| 0.9.4 | 6 / 0 | |
| 0.9.3 | 6 / 0 | |
| 0.9.2 | 6 / 0 | |
| 0.9.1 | 6 / 0 | |
| 0.9.0 | 6 / 0 | |
| 0.8.0 | 6 / 0 | |
| 0.7.6 | 6 / 0 | |
| 0.7.5 | 6 / 0 | |
| 0.7.4 | 6 / 0 | |
| 0.7.3 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.9 | 6 / 0 | |
| 0.6.8 | 6 / 0 | |
| 0.6.7 | 6 / 0 | |
| 0.6.6 | 6 / 0 | |
| 0.6.5 | 6 / 0 | |
| 0.6.4 | 6 / 0 | |
| 0.6.3 | 6 / 0 | |
| 0.6.2 | 3 / 0 | |
| 0.6.1 | 3 / 0 | |
| 0.3.18 | 3 / 0 | |
| 0.3.17 | 3 / 0 | |
| 0.3.16 | 3 / 0 | |
| 0.3.15 | 3 / 0 | |
| 0.3.14 | 3 / 0 | |
| 0.3.13 | 3 / 0 | |
| 0.3.12 | 3 / 0 | |
| 0.3.11 | 3 / 0 | |
| 0.3.10 | 3 / 0 | |
| 0.3.9 | 3 / 0 | |
| 0.3.8 | 3 / 0 | |
| 0.3.7 | 3 / 0 | |
| 0.3.6 | 3 / 0 | |
| 0.3.5 | 3 / 0 | |
| 0.3.4 | 3 / 0 | |
| 0.3.3 | 3 / 0 | |
| 0.3.2 | 3 / 0 | |
| 0.3.1 | 3 / 0 | |
| 0.3.0 | 3 / 0 | |
| 0.2.19 | 3 / 0 | |
| 0.2.18 | 3 / 0 | |
| 0.2.17 | 3 / 0 | |
| 0.2.16 | 3 / 0 | |
| 0.2.15 | 3 / 0 | |
| 0.2.14 | 3 / 0 | |
| 0.2.13 | 3 / 0 | |
| 0.2.12 | 4 / 0 | |
| 0.2.11 | 4 / 0 | |
| 0.2.10 | 4 / 0 | |
| 0.2.9 | 4 / 0 | |
| 0.2.5 | 4 / 0 | |
| 0.2.4 | 4 / 0 | |
| 0.2.3 | 4 / 0 | |
| 0.2.2 | 4 / 0 | |
| 0.2.1 | 4 / 0 | |
| 0.1.13 | 4 / 0 | |
| 0.1.12 | 4 / 0 | |
| 0.1.11 | 4 / 0 | |
| 0.1.10 | 4 / 0 | |
| 0.1.9 | 4 / 0 | |
| 0.1.8 | 4 / 0 | |
| 0.1.7 | 4 / 0 | |
| 0.1.6 | 4 / 0 | |
| 0.1.5 | 4 / 0 | |
| 0.1.4 | 4 / 0 | |
| 0.1.3 | 4 / 0 | |
| 0.1.2 | 4 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.0.85 | 4 / 0 | |
| 0.0.84 | 4 / 0 | |
| 0.0.83 | 4 / 0 | |
| 0.0.82 | 4 / 0 | |
| 0.0.81 | 4 / 0 | |
| 0.0.80 | 4 / 0 | |
| 0.0.79 | 4 / 0 |
v0.9.39
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.38
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.37
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.