@rocket.chat/rest-typings
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@rocket.chat/ui-kit | AI (dependencies): Same-org Rocket.Chat dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@rocket.chat/message-parser | AI (dependencies): Same-org Rocket.Chat dependency; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@rocket.chat/message-parser | AI (phantom-deps): Same-org type-only dependency; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 8.4.3 | 5 / 5 | |
| 8.4.2 | 5 / 5 | |
| 8.4.0 | 5 / 5 | |
| 8.3.5 | 5 / 5 | |
| 8.3.4 | 5 / 5 | |
| 8.3.0 | 5 / 5 | |
| 8.2.5 | 5 / 6 | |
| 8.2.4 | 5 / 6 | |
| 8.1.5 | 5 / 6 | |
| 8.0.6 | 5 / 6 | |
| 7.13.8 | 5 / 7 | |
| 7.12.2 | 5 / 7 | |
| 7.10.12 | 5 / 7 |
v8.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
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 (gazzo) than the most recent previously approved version (rocketchat-buildmaster) on 2026-05-22, but gazzo 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.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.