@visactor/vseed
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; legitimate CI/CD migration for VisActor org. | ai | |
| source-diff | obfuscated-file:dist/cjs/index.cjs | AI (source-diff): Standard rslib/webpack minified bundle; not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/cjs/index.cjs | AI (source-diff): webpack __rslib_import_meta_url__ pattern triggers false positive; no actual network+eval payload present. | ai | |
| source-diff | obfuscated-file:dist/static/js/index.7ac2af0b.js | AI (source-diff): Webpack-minified application bundle; sample shows vseed pipeline logic, not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:remeda | AI (phantom-deps): remeda is a declared runtime dep; phantom-dep heuristic fires because it may be used indirectly or in type-level code. | ai | |
| source-diff | obfuscated-file:dist/static/js/271.b02e15b2.js | AI (source-diff): File is webpack-minified zod library bundle; sample shows recognizable zod internals, not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/static/js/271.b02e15b2.js | AI (source-diff): Same webpack bundle; no actual dropper/loader pattern visible in sample — false positive from minified zod code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): VisActor monorepo package; sparse metadata is typical for internal libs, not spam/malware. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.5.6 | 5 / 16 | |
| 0.5.5 | 5 / 16 | |
| 0.5.4 | 5 / 16 | |
| 0.5.3 | 5 / 16 | |
| 0.5.2 | 5 / 16 | |
| 0.5.1 | 5 / 16 | |
| 0.5.0 | 5 / 21 | |
| 0.4.28 | 5 / 21 | |
| 0.4.27 | 5 / 21 | |
| 0.4.22 | 5 / 21 | |
| 0.4.2 | 4 / 19 | |
| 0.4.1 | 4 / 19 | |
| 0.4.0 | 4 / 19 | |
| 0.3.15 | 4 / 19 | |
| 0.3.14 | 4 / 19 | |
| 0.3.13 | 4 / 19 | |
| 0.3.12 | 4 / 19 | |
| 0.3.11 | 4 / 19 | |
| 0.3.10 | 4 / 19 | |
| 0.3.9 | 4 / 19 | |
| 0.3.8 | 4 / 19 | |
| 0.3.7 | 4 / 19 | |
| 0.3.6 | 4 / 19 | |
| 0.3.5 | 4 / 19 | |
| 0.3.4 | 4 / 19 | |
| 0.3.3 | 4 / 19 | |
| 0.3.2 | 4 / 19 | |
| 0.3.1 | 4 / 19 | |
| 0.3.0 | 4 / 19 | |
| 0.2.9 | 4 / 19 | |
| 0.2.8 | 4 / 19 | |
| 0.2.7 | 4 / 19 | |
| 0.2.6 | 4 / 19 | |
| 0.2.5 | 4 / 19 | |
| 0.2.3 | 4 / 19 | |
| 0.2.2 | 4 / 19 | |
| 0.2.1 | 4 / 19 | |
| 0.2.0 | 4 / 19 | |
| 0.1.51 | 4 / 19 | |
| 0.1.50 | 4 / 19 | |
| 0.1.49 | 4 / 19 | |
| 0.1.48 | 4 / 19 | |
| 0.1.47 | 4 / 19 | |
| 0.1.46 | 4 / 19 | |
| 0.1.45 | 4 / 19 | |
| 0.1.44 | 4 / 19 | |
| 0.1.43 | 4 / 19 | |
| 0.1.42 | 4 / 19 | |
| 0.1.41 | 4 / 19 | |
| 0.1.40 | 4 / 19 | |
| 0.1.39 | 4 / 19 | |
| 0.1.38 | 4 / 19 | |
| 0.0.19 | 2 / 11 | |
| 0.0.18 | 2 / 10 | |
| 0.0.17 | 2 / 10 | |
| 0.0.16 | 2 / 10 | |
| 0.0.15 | 2 / 10 | |
| 0.0.14 | 2 / 10 | |
| 0.0.13 | 2 / 10 | |
| 0.0.12 | 2 / 10 | |
| 0.0.11 | 2 / 10 | |
| 0.0.10 | 2 / 10 | |
| 0.0.9 | 2 / 10 | |
| 0.0.8 | 2 / 10 | |
| 0.0.7 | 2 / 10 | |
| 0.0.6 | 2 / 10 | |
| 0.0.5 | 2 / 10 | |
| 0.0.4 | 2 / 10 | |
| 0.0.3 | 1 / 10 | |
| 0.0.2 | 1 / 10 | |
| 0.0.1 | 0 / 8 |
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (youngwinds) on 2025-12-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.