@blocklet/server-js
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared dep used indirectly via bundled/config references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ocap/util | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:blueimp-md5 | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-app-polyfill | AI (phantom-deps): Declared dep used indirectly; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.17.12 | 12 / 11 | |
| 1.17.11 | 11 / 12 | |
| 1.17.10 | 11 / 12 | |
| 1.17.9 | 11 / 12 | |
| 1.17.8 | 11 / 12 | |
| 1.17.7 | 11 / 12 | |
| 1.17.6 | 11 / 12 | |
| 1.17.5 | 11 / 12 | |
| 1.17.4 | 11 / 12 | |
| 1.17.3 | 11 / 12 | |
| 1.17.2 | 11 / 12 | |
| 1.17.1 | 11 / 12 | |
| 1.17.0 | 11 / 12 |
v1.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.