@roomstay/core
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer matches known team member per provenance audit trail. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team change, not a takeover pattern given provenance context. | ai | |
| phantom-deps | phantom-dep:decimal.js | AI (phantom-deps): decimal.js likely used indirectly via config/build; established library, low risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @roomstay package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 0 / 22 | |
| 0.2.0 | 0 / 22 | |
| 0.1.85 | 0 / 22 | |
| 0.1.84 | 0 / 22 | |
| 0.1.83 | 0 / 22 | |
| 0.1.82 | 0 / 22 | |
| 0.1.81 | 0 / 22 | |
| 0.1.76 | 0 / 22 | |
| 0.1.75 | 0 / 22 | |
| 0.1.74 | 0 / 22 | |
| 0.1.73 | 0 / 22 | |
| 0.1.72 | 0 / 22 | |
| 0.1.71 | 0 / 22 | |
| 0.1.70 | 0 / 22 | |
| 0.1.69 | 0 / 22 | |
| 0.1.68 | 0 / 22 | |
| 0.1.67 | 0 / 22 | |
| 0.1.66 | 0 / 22 | |
| 0.1.65 | 0 / 22 | |
| 0.1.64 | 0 / 22 | |
| 0.1.63 | 0 / 22 | |
| 0.1.62 | 0 / 22 | |
| 0.1.61 | 3 / 19 | |
| 0.1.60 | 0 / 18 | |
| 0.1.59 | 0 / 18 | |
| 0.1.58 | 0 / 18 | |
| 0.1.57 | 0 / 18 | |
| 0.1.56 | 0 / 18 | |
| 0.1.55 | 0 / 18 | |
| 0.1.54 | 0 / 18 | |
| 0.1.53 | 0 / 18 | |
| 0.1.52 | 0 / 18 | |
| 0.1.51 | 0 / 18 | |
| 0.1.50 | 0 / 18 | |
| 0.1.49 | 0 / 18 | |
| 0.1.48 | 0 / 18 | |
| 0.1.47 | 0 / 18 | |
| 0.1.46 | 0 / 18 | |
| 0.1.45 | 0 / 17 | |
| 0.1.44 | 0 / 17 | |
| 0.1.43 | 0 / 17 | |
| 0.1.42 | 0 / 17 | |
| 0.1.41 | 0 / 17 | |
| 0.1.40 | 0 / 17 | |
| 0.1.38 | 0 / 17 | |
| 0.1.33 | 1 / 16 | |
| 0.1.32 | 0 / 15 | |
| 0.1.31 | 0 / 15 | |
| 0.1.30 | 0 / 15 | |
| 0.1.29 | 0 / 15 | |
| 0.1.28 | 0 / 15 |
v0.1.74
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 (rob.ellis) than the most recent previously approved version (lukefranklin) on 2025-12-11, but rob.ellis 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.
v0.1.63
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 (rob.ellis) than the most recent previously approved version (lukefranklin) on 2025-10-06, but rob.ellis 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.
v0.1.59
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 (rob.ellis) than the most recent previously approved version (lukefranklin) on 2025-09-18, but rob.ellis 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.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
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 (lukefranklin) than the most recent previously approved version (rob.ellis) on 2025-04-07, but lukefranklin 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.
v0.1.42
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 (rob.ellis) than the most recent previously approved version (lukefranklin) on 2025-03-31, but rob.ellis 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.
v0.1.41
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 (lukefranklin) than the most recent previously approved version (rob.ellis) on 2025-03-18, but lukefranklin 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.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
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 (anthonydijitally) than the most recent previously approved version (liemnt) on 2024-10-22, but anthonydijitally 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.
v0.1.32
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 (rob.ellis) than the most recent previously approved version (liemnt) on 2024-08-14, but rob.ellis 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.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
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 (liemnt) than the most recent previously approved version (rob.ellis) on 2024-05-14, but liemnt 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.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.