@things-factory/notification
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@things-factory/shell | AI (dependencies): Same-org monorepo sibling, versioned in lockstep. | ai | |
| dependencies | unvetted-dep:@things-factory/organization | AI (dependencies): Same-org monorepo sibling, versioned in lockstep. | ai | |
| dependencies | unvetted-dep:@things-factory/auth-base | AI (dependencies): Same-org monorepo sibling, versioned in lockstep. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Migration loader resolves local file paths; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 983 versions; no provenance has never been provided and is not a new risk. | ai | |
| phantom-deps | phantom-dep:google | AI (phantom-deps): Declared as dep for config/plugin use; phantom-dep heuristic fires but not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/codelingua | AI (phantom-deps): Same-org package used transitively; stable false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org package used transitively; stable false positive for this ecosystem. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 9.2.33 | 12 / 0 | |
| 9.2.30 | 12 / 0 | |
| 9.2.29 | 12 / 0 | |
| 9.2.24 | 12 / 0 | |
| 9.2.17 | 12 / 0 | |
| 9.2.16 | 12 / 0 | |
| 9.2.5 | 12 / 0 | |
| 9.1.0 | 12 / 0 | |
| 9.0.41 | 12 / 0 | |
| 9.0.36 | 12 / 0 | |
| 9.0.34 | 12 / 0 | |
| 9.0.25 | 12 / 0 | |
| 9.0.24 | 12 / 0 | |
| 9.0.20 | 12 / 0 | |
| 9.0.5 | 12 / 0 | |
| 9.0.2 | 12 / 0 | |
| 9.0.0 | 12 / 0 | |
| 8.0.88 | 12 / 0 | |
| 8.0.87 | 12 / 0 | |
| 8.0.86 | 12 / 0 | |
| 8.0.76 | 12 / 0 | |
| 8.0.75 | 12 / 0 | |
| 8.0.74 | 12 / 0 | |
| 8.0.64 | 12 / 0 | |
| 8.0.63 | 12 / 0 | |
| 4.3.815 | 11 / 0 | |
| 4.3.767 | 11 / 0 | |
| 4.3.764 | 11 / 0 | |
| 4.3.755 | 11 / 0 | |
| 4.3.752 | 11 / 0 | |
| 4.3.743 | 11 / 0 | |
| 4.3.740 | 11 / 0 | |
| 4.3.695 | 11 / 0 | |
| 4.3.689 | 11 / 0 |
v9.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.815
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 (horwengliang95) than the most recent previously approved version (nalshya113) on 2026-04-16, but horwengliang95 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.767
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-29, but wengliang95 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.764
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-28, but wengliang95 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.755
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-20, but wengliang95 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.752
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-15, but wengliang95 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.743
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-08, but wengliang95 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.740
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 (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-05, but wengliang95 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.695
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 (horwengliang95) than the most recent previously approved version (nalshya113) on 2025-11-21, but horwengliang95 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.689
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 (horwengliang95) than the most recent previously approved version (heartyoh) on 2025-11-02, but horwengliang95 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.