@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 — 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 |
|---|---|---|---|---|
| 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/i18n-base | AI (phantom-deps): Same-org package used transitively; stable false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@things-factory/codelingua | AI (phantom-deps): Same-org package used transitively; stable false positive for this ecosystem. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 12 / 0 | |
| 9.2.17 | 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 |
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.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.
v8.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.