react-swipeable-views
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-addons-shallow-compare | AI (phantom-deps): Used in compiled lib output, not scannable in minified build. | ai | |
| phantom-deps | phantom-dep:keycode | AI (phantom-deps): Used in compiled lib output, not scannable in minified build. | ai | |
| phantom-deps | phantom-dep:react-event-listener | AI (phantom-deps): Used in compiled lib output, not scannable in minified build. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): babel-plugin-preval dev tooling pattern, not runtime-executed malicious code. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publisher change (2376d), consistent with legitimate handoff not compromise. | ai | |
| provenance | missing-githead | AI (provenance): Old package predates provenance tooling; publisher has strong track record. | ai | |
| source-diff | obfuscated-file-transition:lib/SwipeableViews.js | AI (source-diff): Standard Babel-compiled CJS output from 2016, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime used implicitly by Babel-compiled output, common false positive. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): object-assign is a trivial, universally trusted micro-dependency. | ai | |
| source-diff | obfuscated-file:docs/dist/app.js | AI (source-diff): Webpack-bundled docs demo output, not obfuscation/malware. | ai | |
| source-diff | net-exec-file:docs/dist/app.js | AI (source-diff): React/webpack bundle for docs site, no real net+exec dropper behavior. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Increase is the bundled docs demo, not injected payload. | ai | |
| phantom-deps | phantom-dep:react-swipeable-views-utils | AI (phantom-deps): Sibling monorepo package; referenced in config but not directly imported is expected for this package structure. | ai |
Versions (showing 51 of 99)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 5 / 1 | |
| 0.14.1 | 5 / 1 | |
| 0.14.0 | 5 / 1 | |
| 0.13.9 | 5 / 1 | |
| 0.13.8 | 5 / 1 | |
| 0.13.7 | 6 / 1 | |
| 0.13.6 | 6 / 1 | |
| 0.13.5 | 1 / 63 | |
| 0.13.4 | 6 / 1 | |
| 0.13.3 | 6 / 1 | |
| 0.13.1 | 6 / 1 | |
| 0.13.0 | 6 / 1 | |
| 0.12.18 | 6 / 1 | |
| 0.12.17 | 6 / 1 | |
| 0.12.16 | 6 / 1 | |
| 0.12.15 | 6 / 1 | |
| 0.12.14 | 6 / 1 | |
| 0.12.13 | 6 / 1 | |
| 0.12.12 | 6 / 1 | |
| 0.12.11 | 6 / 1 | |
| 0.12.10 | 6 / 1 | |
| 0.12.9 | 6 / 1 | |
| 0.12.8 | 6 / 1 | |
| 0.12.7 | 6 / 1 | |
| 0.12.6 | 6 / 1 | |
| 0.12.5 | 6 / 1 | |
| 0.12.4 | 6 / 1 | |
| 0.12.3 | 6 / 1 | |
| 0.12.2 | 6 / 1 | |
| 0.12.1 | 6 / 1 | |
| 0.12.0 | 6 / 1 | |
| 0.11.2 | 5 / 1 | |
| 0.11.1 | 5 / 1 | |
| 0.11.0 | 5 / 1 | |
| 0.10.8 | 5 / 1 | |
| 0.10.7 | 5 / 1 | |
| 0.10.6 | 5 / 1 | |
| 0.10.5 | 5 / 1 | |
| 0.10.4 | 5 / 1 | |
| 0.10.3 | 5 / 1 | |
| 0.10.2 | 5 / 1 | |
| 0.10.1 | 5 / 1 | |
| 0.10.0 | 5 / 1 | |
| 0.9.3 | 4 / 1 | |
| 0.9.2 | 3 / 1 | |
| 0.9.1 | 6 / 1 | |
| 0.9.0 | 6 / 1 | |
| 0.8.3 | 7 / 54 | |
| 0.8.1 | 5 / 53 | |
| 0.8.0 | 5 / 53 | |
| 0.7.11 | 5 / 54 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oliviertassinari) than the most recent previously approved version (jeanpoelie) on 2020-02-01, but oliviertassinari is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jeanpoelie) than the most recent previously approved version (oliviertassinari) on 2020-01-26, but jeanpoelie is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jeanpoelie.
This version was published by a different npm account (jeanpoelie) than the most recent previously approved version (oliviertassinari) on 2020-01-21. It has since remained available on npm for 2376 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: oliviertassinari.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.