@reboot-dev/reboot-std-api
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:presence/mouse_tracker/v1/mouse_position_rbt.js | AI (source-diff): Encoded strings are gzip-compressed protobuf descriptors passed to importPy; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:collections/ordered_map/v1/ordered_map_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| source-diff | encoded-string-file:presence/v1/presence_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| source-diff | encoded-string-file:pubsub/v1/pubsub_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| source-diff | encoded-string-file:collections/queue/v1/queue_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| source-diff | encoded-string-file:collections/v1/sorted_map_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| source-diff | encoded-string-file:presence/subscriber/v1/subscriber_rbt.js | AI (source-diff): Same importPy protobuf descriptor pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@scarf/scarf | AI (phantom-deps): Scarf is a telemetry tool often referenced in config without direct import; stable false positive. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 1 | |
| 0.46.0 | 1 / 1 | |
| 0.45.2 | 1 / 1 | |
| 0.45.1 | 1 / 1 | |
| 0.44.0 | 1 / 1 | |
| 0.43.0 | 1 / 1 | |
| 0.42.0 | 1 / 1 | |
| 0.41.0 | 1 / 1 | |
| 0.40.1 | 1 / 1 | |
| 0.40.0 | 1 / 1 | |
| 0.39.3 | 1 / 1 | |
| 0.39.2 | 1 / 1 | |
| 0.39.1 | 1 / 1 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
9 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
8 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.