slate-hyperscript
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; no code changes, benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): Legacy manual publish flow; stable across versions. | ai | |
| source-diff | obfuscated-file:lib/index.js | AI (source-diff): Babel-transpiled CJS build output with readable identifiers, not obfuscation. | ai | |
| phantom-deps | phantom-dep:slate-dev-logger | AI (phantom-deps): Legit dep not surfaced in bundled/transpiled import scan. | ai | |
| source-diff | obfuscated-file-transition:lib/index.js | AI (source-diff): Babel-transpiled build output, not obfuscation; readable requires and named exports, no payload. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate CI/CD migration; SLSA attestation confirms automated publish from the same repo. | ai |
Versions (showing 100 of 194)
| Version | Deps | Published |
|---|---|---|
| 0.125.0 | 0 / 3 | |
| 0.115.0 | 0 / 3 | |
| 0.100.0 | 1 / 3 | |
| 0.81.3 | 1 / 3 | |
| 0.77.0 | 1 / 3 | |
| 0.67.0 | 1 / 3 | |
| 0.66.0 | 1 / 3 | |
| 0.62.0 | 1 / 1 | |
| 0.61.3 | 1 / 1 | |
| 0.61.0 | 1 / 1 | |
| 0.60.17 | 1 / 1 | |
| 0.60.11 | 1 / 1 | |
| 0.60.9 | 1 / 1 | |
| 0.60.8 | 1 / 1 | |
| 0.60.4 | 1 / 1 | |
| 0.60.3 | 1 / 1 | |
| 0.60.2 | 1 / 1 | |
| 0.60.1 | 1 / 1 | |
| 0.60.0 | 1 / 1 | |
| 0.59.0 | 1 / 1 | |
| 0.58.4 | 1 / 1 | |
| 0.58.3 | 1 / 1 | |
| 0.58.1 | 1 / 1 | |
| 0.58.0 | 1 / 1 | |
| 0.57.3 | 1 / 1 | |
| 0.57.2 | 1 / 1 | |
| 0.57.1 | 1 / 1 | |
| 0.57.0 | 1 / 1 | |
| 0.56.1 | 1 / 1 | |
| 0.56.0 | 1 / 1 | |
| 0.55.3 | 1 / 1 | |
| 0.55.2 | 1 / 1 | |
| 0.55.1 | 1 / 1 | |
| 0.55.0 | 1 / 1 | |
| 0.54.6 | 1 / 1 | |
| 0.54.5 | 1 / 1 | |
| 0.54.4 | 1 / 1 | |
| 0.54.3 | 1 / 1 | |
| 0.54.2 | 1 / 1 | |
| 0.54.1 | 1 / 1 | |
| 0.54.0 | 1 / 1 | |
| 0.53.0 | 1 / 1 | |
| 0.52.6 | 1 / 1 | |
| 0.52.5 | 1 / 1 | |
| 0.52.4 | 1 / 1 | |
| 0.52.3 | 1 / 1 | |
| 0.52.2 | 1 / 1 | |
| 0.52.1 | 1 / 1 | |
| 0.52.0 | 1 / 1 | |
| 0.51.0 | 1 / 1 | |
| 0.50.8 | 1 / 1 | |
| 0.50.7 | 1 / 1 | |
| 0.50.6 | 1 / 1 | |
| 0.50.5 | 1 / 1 | |
| 0.50.4 | 1 / 1 | |
| 0.50.3 | 1 / 1 | |
| 0.50.2 | 1 / 1 | |
| 0.50.1 | 1 / 1 | |
| 0.50.0 | 1 / 1 | |
| 0.13.9 | 1 / 2 | |
| 0.13.8 | 1 / 2 | |
| 0.13.7 | 1 / 2 | |
| 0.13.6 | 1 / 2 | |
| 0.13.5 | 1 / 2 | |
| 0.13.4 | 1 / 2 | |
| 0.13.3 | 1 / 2 | |
| 0.13.2 | 1 / 2 | |
| 0.13.1 | 1 / 2 | |
| 0.13.0 | 1 / 2 | |
| 0.12.1 | 1 / 2 | |
| 0.12.0 | 1 / 2 | |
| 0.11.30 | 1 / 2 | |
| 0.11.29 | 1 / 2 | |
| 0.11.28 | 1 / 2 | |
| 0.11.27 | 1 / 2 | |
| 0.11.26 | 1 / 2 | |
| 0.11.25 | 1 / 2 | |
| 0.11.24 | 1 / 2 | |
| 0.11.23 | 1 / 2 | |
| 0.11.22 | 1 / 2 | |
| 0.11.21 | 1 / 2 | |
| 0.11.20 | 1 / 2 | |
| 0.11.19 | 1 / 2 | |
| 0.11.18 | 1 / 2 | |
| 0.11.17 | 1 / 2 | |
| 0.11.16 | 1 / 2 | |
| 0.11.15 | 1 / 2 | |
| 0.11.14 | 1 / 2 | |
| 0.11.13 | 1 / 2 | |
| 0.11.12 | 1 / 2 | |
| 0.11.11 | 1 / 2 | |
| 0.11.10 | 1 / 2 | |
| 0.11.9 | 1 / 2 | |
| 0.11.8 | 1 / 2 | |
| 0.11.7 | 1 / 2 | |
| 0.11.6 | 1 / 2 | |
| 0.11.5 | 1 / 2 | |
| 0.11.4 | 1 / 2 | |
| 0.11.3 | 1 / 2 | |
| 0.11.2 | 1 / 2 |
v0.81.3
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 (ianstormtaylor) than the most recent previously approved version (thesunny) on 2022-07-22, but ianstormtaylor 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.77.0
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 (ianstormtaylor) than the most recent previously approved version (thesunny) on 2022-04-13, but ianstormtaylor 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.67.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: ianstormtaylor.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ianstormtaylor) than the most recent previously approved version (thesunny) on 2021-10-18, but ianstormtaylor 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.66.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: ianstormtaylor.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ianstormtaylor) than the most recent previously approved version (thesunny) on 2021-09-13, but ianstormtaylor 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.62.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: ianstormtaylor.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ianstormtaylor) than the most recent previously approved version (thesunny) on 2021-04-01, but ianstormtaylor 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.61.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
2 findingsThis version was published by a different npm account (thesunny) than the most recent previously approved version (damareyoh) on 2020-11-24. It has since remained available on npm for 2064 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.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.3
2 findingsThis version was published by a different npm account (damareyoh) than the most recent previously approved version (ianstormtaylor) on 2020-05-05. It has since remained available on npm for 2268 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.57.2
2 findingsThis version was published by a different npm account (damareyoh) than the most recent previously approved version (ianstormtaylor) on 2020-04-24. It has since remained available on npm for 2278 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.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage 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.2
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.