@rotorsoft/act
act core library
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:react | AI (typosquat): Scoped package @rotorsoft/act; name collision with react is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @rotorsoft/act; name collision with got is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @rotorsoft/act; name collision with ajv is coincidental, not impersonation. | ai |
Versions (showing 51 of 124)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 1 / 1 | |
| 1.9.0 | 1 / 1 | |
| 1.8.0 | 1 / 1 | |
| 1.7.0 | 1 / 1 | |
| 1.6.0 | 1 / 1 | |
| 1.5.2 | 1 / 1 | |
| 1.5.1 | 1 / 1 | |
| 1.5.0 | 1 / 1 | |
| 1.4.0 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.0 | 1 / 1 | |
| 0.46.0 | 1 / 1 | |
| 0.45.0 | 1 / 1 | |
| 0.44.0 | 1 / 1 | |
| 0.43.0 | 1 / 1 | |
| 0.42.0 | 1 / 1 | |
| 0.41.0 | 1 / 1 | |
| 0.40.0 | 1 / 1 | |
| 0.39.0 | 1 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.0 | 1 / 0 | |
| 0.36.0 | 1 / 0 | |
| 0.35.2 | 1 / 0 | |
| 0.35.1 | 1 / 0 | |
| 0.35.0 | 1 / 0 | |
| 0.34.0 | 1 / 0 | |
| 0.33.3 | 1 / 0 | |
| 0.33.2 | 2 / 0 | |
| 0.33.1 | 2 / 0 | |
| 0.33.0 | 2 / 0 | |
| 0.32.7 | 2 / 0 | |
| 0.32.6 | 2 / 0 | |
| 0.32.5 | 2 / 0 | |
| 0.32.4 | 2 / 0 | |
| 0.32.3 | 2 / 0 | |
| 0.32.2 | 2 / 0 | |
| 0.32.1 | 2 / 0 | |
| 0.32.0 | 2 / 0 | |
| 0.31.1 | 2 / 0 | |
| 0.31.0 | 2 / 0 | |
| 0.30.1 | 2 / 0 | |
| 0.30.0 | 2 / 0 | |
| 0.29.1 | 2 / 0 | |
| 0.29.0 | 2 / 0 | |
| 0.28.0 | 2 / 0 | |
| 0.27.0 | 2 / 0 | |
| 0.26.1 | 2 / 0 | |
| 0.26.0 | 2 / 0 | |
| 0.25.2 | 2 / 0 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.