@seayoo-web/scripts
scripts for seayoo web repos
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stylelint-config-standard | AI (phantom-deps): Config-referenced stylelint preset; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:stylelint-config-recess-order | AI (phantom-deps): Config-referenced stylelint preset; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:stylelint-order | AI (phantom-deps): Config-file reference in a build-scripts package; not a direct import, stable pattern. | ai | |
| phantom-deps | phantom-dep:postcss-html | AI (phantom-deps): Config-file reference in a build-scripts package; not a direct import, stable pattern. | ai | |
| phantom-deps | phantom-dep:vite-plugin-stylelint | AI (phantom-deps): Config-file reference in a build-scripts package; not a direct import, stable pattern. | ai | |
| phantom-deps | phantom-dep:terser | AI (phantom-deps): terser is a declared runtime dep consumed by vite/rollup config, not direct import — stable FP for this build-tool package. | ai | |
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): stylelint is a declared runtime dep used via config files, not direct import — stable FP for this build-tool package. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): jiti is a declared runtime dep used via config file loading, not direct import — stable FP for this build-tool package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.3.7 | 21 / 4 | |
| 4.3.6 | 21 / 4 | |
| 4.3.5 | 21 / 4 | |
| 4.3.4 | 21 / 4 | |
| 4.3.3 | 21 / 4 | |
| 4.3.2 | 21 / 4 | |
| 4.3.1 | 21 / 4 | |
| 4.3.0 | 21 / 4 | |
| 4.2.0 | 21 / 4 | |
| 4.1.2 | 20 / 4 | |
| 4.1.1 | 20 / 4 | |
| 4.1.0 | 20 / 4 | |
| 4.0.4 | 16 / 4 | |
| 4.0.3 | 16 / 4 | |
| 4.0.2 | 16 / 4 | |
| 4.0.1 | 16 / 4 | |
| 4.0.0 | 16 / 4 | |
| 3.1.11 | 21 / 9 | |
| 3.1.10 | 21 / 9 | |
| 3.1.9 | 21 / 9 | |
| 3.1.8 | 21 / 9 | |
| 3.1.7 | 21 / 9 | |
| 3.1.6 | 21 / 9 |
v4.3.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 (niboac) than the most recent previously approved version (zjcn5205) on 2026-05-26, but niboac 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.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
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 (niboac) than the most recent previously approved version (zjcn5205) on 2026-04-15, but niboac 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.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.