@procore/bim-webviewer-sdk
Procore BIM Webviewer SDK
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
Keywords
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 17.8.0 | 0 / 0 | |
| 17.7.0 | 0 / 0 | |
| 17.6.0 | 0 / 0 | |
| 17.5.0 | 0 / 0 | |
| 17.4.0 | 0 / 0 | |
| 17.3.0 | 0 / 0 | |
| 17.2.1 | 0 / 0 | |
| 17.2.0 | 0 / 0 | |
| 17.1.0 | 0 / 0 | |
| 17.0.0 | 0 / 0 |
v17.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
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 (procore-npm-bot) than the most recent previously approved version (sseanwang) on 2024-12-16, but procore-npm-bot 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.
v17.1.0
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 (sseanwang) than the most recent previously approved version (procore-npm-bot) on 2024-12-10, but sseanwang 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.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.