@live-change/filesystem-plugin
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used intentionally to compile user-supplied filter predicates; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo plugin; sparse metadata is expected and consistent across all versions. | ai | |
| phantom-deps | phantom-dep:blue-tape | AI (phantom-deps): blue-tape is a test runner referenced in the test script; not imported directly in source. | ai |
Versions (showing 30 of 130)
| Version | Deps | Published |
|---|---|---|
| 0.9.100 | 2 / 0 | |
| 0.9.99 | 2 / 0 | |
| 0.9.98 | 2 / 0 | |
| 0.9.97 | 2 / 0 | |
| 0.9.96 | 2 / 0 | |
| 0.9.95 | 2 / 0 | |
| 0.9.94 | 2 / 0 | |
| 0.9.93 | 2 / 0 | |
| 0.9.92 | 2 / 0 | |
| 0.9.91 | 2 / 0 | |
| 0.9.90 | 2 / 0 | |
| 0.9.89 | 2 / 0 | |
| 0.9.88 | 2 / 0 | |
| 0.9.87 | 2 / 0 | |
| 0.9.86 | 2 / 0 | |
| 0.9.85 | 2 / 0 | |
| 0.9.84 | 2 / 0 | |
| 0.9.83 | 2 / 0 | |
| 0.9.82 | 2 / 0 | |
| 0.9.81 | 2 / 0 | |
| 0.9.80 | 2 / 0 | |
| 0.9.79 | 2 / 0 | |
| 0.9.78 | 2 / 0 | |
| 0.9.77 | 2 / 0 | |
| 0.9.76 | 2 / 0 | |
| 0.9.75 | 2 / 0 | |
| 0.9.74 | 2 / 0 | |
| 0.9.73 | 2 / 0 | |
| 0.9.72 | 2 / 0 | |
| 0.9.71 | 2 / 0 |
v0.9.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.