@harmoniclabs/buildooor No license 29 versions

@harmoniclabs/buildooor

npm Repository Homepage

29

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

harmonicpool

Keywords

cardanoplutusblockchainoffchainadadApp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@harmoniclabs/cbor	AI (dependencies): Same-org dependency from HarmonicLabs; consistent with this package's established dependency graph.	ai	2026/05/14
dependencies	unvetted-dep:@harmoniclabs/crypto	AI (dependencies): Same-org dependency from HarmonicLabs; consistent with this package's established dependency graph.	ai	2026/05/14
dependencies	unvetted-dep:@harmoniclabs/plutus-data	AI (dependencies): Same-org dependency from HarmonicLabs; consistent with this package's established dependency graph.	ai	2026/05/14
publish-pattern	dormant-publish	AI (publish-pattern): Publisher has 21 approved packages and 1110-day history; inactivity gap is plausible for a niche Cardano library, not indicative of takeover.	ai	2026/05/14
phantom-deps	phantom-dep:@harmoniclabs/pair	AI (phantom-deps): Same-org dependency; heuristic false positive for this package's import structure.	ai	2026/05/14
phantom-deps	phantom-dep:@harmoniclabs/bigint-utils	AI (phantom-deps): Same-org dependency; heuristic false positive for this package's import structure.	ai	2026/05/14

Versions (showing 29 of 29)

Version	Deps	Published
0.2.7	13 / 8	2026-04-23
0.2.6	13 / 8	2026-03-18
0.2.5	13 / 8	2026-03-17
0.2.4	13 / 8	2026-03-17
0.2.3	13 / 8	2026-03-17
0.2.2	13 / 8	2026-03-17
0.2.1	13 / 8	2026-03-16
0.2.0	13 / 8	2026-03-16
0.1.31	13 / 8	2026-02-20
0.1.30	13 / 8	2026-02-20
0.1.29	13 / 8	2026-02-15
0.1.28	13 / 8	2026-02-09
0.1.27	13 / 8	2026-02-09
0.1.26	13 / 8	2026-02-09
0.1.25	13 / 8	2026-02-09
0.1.24	13 / 8	2026-02-09
0.1.23	13 / 8	2026-02-03
0.1.22	13 / 8	2026-01-16
0.1.21	13 / 8	2025-12-20
0.1.20	13 / 8	2025-08-10
0.1.19	13 / 8	2025-07-29
0.1.18	13 / 8	2025-07-29
0.1.17	13 / 8	2025-07-28
0.1.16	13 / 8	2025-07-02
0.1.15	13 / 8	2025-07-01
0.1.14	13 / 8	2025-06-24
0.1.13	13 / 8	2025-06-24
0.1.12	13 / 8	2025-06-24
0.1.11	13 / 8	2025-06-23

v0.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.