@xapp/arachne-parsers
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.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Change is to CI/CD (GitHub Actions) publishing, not a suspicious manual account. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with 62 versions and 2000+ day history; missing public metadata is a style choice, not a malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-lived scoped org package; missing description is consistent across versions, not a red flag. | ai | |
| phantom-deps | phantom-dep:@types/cheerio | AI (phantom-deps): @types/cheerio is a type-only package loaded by convention; not directly imported at runtime. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 4 / 15 | |
| 1.14.0 | 4 / 15 | |
| 1.13.0 | 4 / 15 | |
| 1.12.0 | 4 / 15 | |
| 1.11.0 | 4 / 15 | |
| 1.10.9 | 4 / 15 | |
| 1.10.7 | 4 / 15 | |
| 1.10.1 | 4 / 15 | |
| 1.10.0 | 4 / 15 | |
| 1.9.2 | 4 / 15 | |
| 1.9.1 | 4 / 15 | |
| 1.9.0 | 4 / 15 | |
| 1.8.13 | 4 / 15 | |
| 1.8.12 | 4 / 15 | |
| 1.8.9 | 4 / 15 | |
| 1.8.8 | 4 / 15 | |
| 1.8.7 | 4 / 15 | |
| 1.8.5 | 4 / 15 | |
| 1.8.4 | 4 / 15 | |
| 1.8.2 | 4 / 15 | |
| 1.8.1 | 4 / 15 | |
| 1.8.0 | 4 / 15 | |
| 1.7.5 | 4 / 15 | |
| 1.7.4 | 4 / 15 | |
| 1.7.3 | 4 / 15 | |
| 1.7.2 | 4 / 15 | |
| 1.7.0 | 4 / 15 | |
| 1.6.2 | 4 / 15 | |
| 1.6.1 | 4 / 15 | |
| 1.6.0 | 4 / 15 | |
| 1.5.0 | 4 / 15 | |
| 1.4.0 | 4 / 15 | |
| 1.3.4 | 4 / 15 | |
| 1.3.3 | 4 / 15 | |
| 1.3.1 | 4 / 15 | |
| 1.3.0 | 4 / 15 | |
| 1.2.2 | 4 / 15 | |
| 1.2.0 | 4 / 15 | |
| 1.1.1 | 4 / 15 | |
| 1.1.0 | 4 / 15 |
v1.15.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
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.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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.2
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.