@mybricks/sdk-for-app
SDK for application UI
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
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 material code change vs prior approved version. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Transition already vetted across 14 prior approved versions; no new signal this version. | ai | |
| provenance | publisher-changed | AI (provenance): Historical transition predating many approved versions; unchanged provenance vs prior approved. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same historical transition, not a fresh event. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Intentional remote script execution pattern in a low-code SDK; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 314 versions; lack of Sigstore attestation is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-to-image | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dom-to-image | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:html-webpack-plugin | AI (phantom-deps): SDK package pattern — deps declared for consumer use or dynamic loading, not direct imports. Stable false positive for this package. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 1.0.78 | 6 / 33 | |
| 1.0.77 | 6 / 33 | |
| 1.0.76 | 6 / 33 | |
| 1.0.75 | 6 / 33 | |
| 1.0.74 | 6 / 33 | |
| 1.0.73 | 6 / 33 | |
| 1.0.72 | 6 / 33 | |
| 1.0.71 | 6 / 33 | |
| 1.0.70 | 6 / 33 | |
| 1.0.69 | 6 / 33 | |
| 1.0.68 | 6 / 33 | |
| 1.0.67 | 6 / 33 | |
| 1.0.66 | 6 / 33 | |
| 1.0.65 | 6 / 33 | |
| 1.0.64 | 6 / 33 | |
| 1.0.63 | 6 / 33 | |
| 1.0.62 | 6 / 33 | |
| 1.0.61 | 6 / 33 | |
| 1.0.60 | 6 / 33 | |
| 1.0.59 | 6 / 33 | |
| 1.0.58 | 6 / 33 | |
| 1.0.57 | 5 / 33 | |
| 1.0.56 | 5 / 33 | |
| 1.0.55 | 5 / 33 | |
| 1.0.54 | 5 / 33 | |
| 1.0.53 | 5 / 33 | |
| 1.0.52 | 5 / 33 | |
| 1.0.51 | 5 / 33 | |
| 1.0.50 | 5 / 33 | |
| 1.0.49 | 5 / 33 | |
| 1.0.48 | 5 / 33 | |
| 1.0.47 | 5 / 33 | |
| 1.0.46 | 5 / 33 | |
| 1.0.45 | 5 / 33 | |
| 1.0.44 | 5 / 33 | |
| 1.0.43 | 5 / 33 | |
| 1.0.42 | 5 / 33 | |
| 1.0.41 | 5 / 33 | |
| 1.0.40 | 5 / 33 | |
| 1.0.39 | 5 / 33 | |
| 1.0.38 | 5 / 33 | |
| 1.0.37 | 5 / 33 | |
| 1.0.36 | 5 / 33 | |
| 1.0.35 | 5 / 33 | |
| 1.0.34 | 5 / 33 | |
| 1.0.33 | 5 / 33 | |
| 1.0.32 | 5 / 33 | |
| 1.0.31 | 5 / 33 | |
| 1.0.30 | 5 / 33 | |
| 1.0.29 | 5 / 33 | |
| 1.0.28 | 5 / 33 | |
| 1.0.27 | 5 / 33 | |
| 1.0.26 | 5 / 33 | |
| 1.0.25 | 4 / 34 | |
| 1.0.24 | 4 / 34 | |
| 1.0.23 | 4 / 34 | |
| 1.0.22 | 4 / 34 | |
| 1.0.20 | 4 / 34 | |
| 1.0.19 | 4 / 34 | |
| 1.0.18 | 4 / 34 | |
| 1.0.17 | 4 / 34 | |
| 1.0.16 | 4 / 34 | |
| 1.0.15 | 4 / 34 | |
| 1.0.14 | 4 / 34 | |
| 1.0.13 | 4 / 34 | |
| 1.0.12 | 4 / 34 | |
| 1.0.11 | 4 / 34 | |
| 1.0.10 | 4 / 34 | |
| 1.0.9 | 4 / 34 | |
| 1.0.8 | 4 / 34 | |
| 1.0.7 | 4 / 34 | |
| 1.0.6 | 4 / 34 | |
| 1.0.5 | 4 / 34 | |
| 1.0.4 | 4 / 34 | |
| 1.0.3 | 4 / 34 | |
| 1.0.2 | 4 / 34 | |
| 1.0.1 | 4 / 34 | |
| 1.0.0 | 3 / 34 |
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (mybricks-group) on 2024-10-17, but leon_js 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.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mybricks-group) than the most recent previously approved version (cocolbell) on 2024-09-21, but mybricks-group 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.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cocolbell) than the most recent previously approved version (jidan.wd) on 2024-07-23, but cocolbell 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.
v1.0.46
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cocolbell) than the most recent previously approved version (jidan.wd) on 2024-07-23, but cocolbell 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.
v1.0.45
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jidan.wd) than the most recent previously approved version (godstream) on 2024-07-17, but jidan.wd 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.
v1.0.44
2 findingsThis version was published by a different npm account than previous versions on 2024-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (godstream) than the most recent previously approved version (jidan.wd) on 2024-07-15, but godstream 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.
v1.0.42
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (letterletter) than the most recent previously approved version (jidan.wd) on 2024-07-09, but letterletter 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.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jidan.wd) than the most recent previously approved version (leo306) on 2024-06-03, but jidan.wd 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.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (godstream) on 2024-04-11, but leo306 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.
v1.0.35
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (godstream) than the most recent previously approved version (leo306) on 2024-04-07, but godstream 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.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2024-03-25, but andyzou 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.
v1.0.32
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2024-02-21, but andyzou 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.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (leon_js) on 2024-01-30, but leo306 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.
v1.0.26
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (leon_js) on 2024-01-30, but leo306 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.
v1.0.25
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (leo306) on 2024-01-30, but leon_js 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.
v1.0.24
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (leo306) on 2024-01-17, but leon_js 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.
v1.0.23
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (leon_js) on 2024-01-03, but leo306 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.
v1.0.22
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (leon_js) on 2024-01-03, but leo306 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.
v1.0.20
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (leo306) on 2023-12-12, but leon_js 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.
v1.0.19
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (leo306) on 2023-12-12, but leon_js 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.
v1.0.18
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (leon_js) on 2023-12-06, but leo306 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.
v1.0.17
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-27, but andyzou 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.
v1.0.16
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-27, but andyzou 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.
v1.0.15
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-21, but andyzou 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.
v1.0.14
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-17, but andyzou 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.
v1.0.13
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-17, but andyzou 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.
v1.0.12
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leon_js) on 2023-11-17, but andyzou 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.
v1.0.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leon_js) than the most recent previously approved version (leo306) on 2023-11-17, but leon_js 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.
v1.0.10
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-16, but andyzou 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.
v1.0.9
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-16, but andyzou 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.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-10, but andyzou 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.
v1.0.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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-10, but andyzou 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.
v1.0.4
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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-08, but andyzou 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.
v1.0.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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-08, but andyzou 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.
v1.0.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: andyzou.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andyzou) than the most recent previously approved version (leo306) on 2023-11-08, but andyzou 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.
v1.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (leo306) than the most recent previously approved version (andyzou) on 2023-11-01, but leo306 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.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.