@builder6/rooms
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Pattern across @builder6 packages; not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is consistent across 138 published versions; not indicative of malicious intent. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom declared as dependency and used in React rendering context; config-only reference is expected for this package type. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): tailwindcss referenced in config files only; standard pattern for packages that bundle Tailwind styles. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 11 / 1 | |
| 3.2.12 | 11 / 1 | |
| 3.2.3 | 11 / 1 | |
| 3.2.1 | 11 / 1 | |
| 3.2.0 | 11 / 1 | |
| 3.1.2 | 11 / 1 | |
| 3.1.1 | 11 / 1 | |
| 3.1.0 | 11 / 1 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.