@tarojs/router-rn
Taro-router-rn
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/view/BackButton.d.ts | AI (source-diff): Base64 image data URI in a .d.ts asset, not obfuscated logic. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lodash is a well-known, widely-vetted dependency. | ai | |
| phantom-deps | phantom-dep:react-native-screens | AI (phantom-deps): Platform-specific peer dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:react-native-gesture-handler | AI (phantom-deps): Platform-specific peer dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@react-native-masked-view/masked-view | AI (phantom-deps): Platform-specific peer dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Utility dep used in config/build context; stable false positive for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 7 / 4 | |
| 4.2.0 | 7 / 4 | |
| 4.1.11 | 7 / 4 | |
| 4.1.10 | 7 / 4 | |
| 4.1.9 | 7 / 4 | |
| 4.1.8 | 7 / 4 | |
| 4.1.7 | 7 / 4 | |
| 4.1.6 | 7 / 4 | |
| 4.1.5 | 7 / 4 | |
| 4.1.4 | 7 / 4 | |
| 4.1.3 | 7 / 4 | |
| 4.1.2 | 7 / 5 | |
| 4.1.1 | 7 / 5 | |
| 4.1.0 | 7 / 5 | |
| 4.0.13 | 7 / 5 | |
| 4.0.12 | 7 / 5 | |
| 4.0.11 | 7 / 5 | |
| 4.0.10 | 7 / 5 | |
| 4.0.9 | 7 / 5 | |
| 4.0.8 | 7 / 5 | |
| 4.0.7 | 10 / 2 | |
| 4.0.6 | 9 / 2 | |
| 4.0.5 | 9 / 2 | |
| 4.0.4 | 9 / 2 | |
| 4.0.3 | 9 / 2 | |
| 4.0.2 | 9 / 2 | |
| 4.0.1 | 11 / 5 | |
| 4.0.0 | 9 / 2 | |
| 3.6.40 | 11 / 5 | |
| 3.6.39 | 11 / 5 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.