@zthun/romulator-api MIT 32 versions

@zthun/romulator-api

npm Repository Homepage

A service for your rom directory for managing media and the directory structure.

32

Versions

MIT

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

zthun

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:reflect-metadata	AI (phantom-deps): reflect-metadata is a well-known implicit runtime dep for NestJS/TypeScript decorator-based apps; not directly imported by design.	ai	2026/04/29
phantom-deps	phantom-dep:rxjs	AI (phantom-deps): rxjs is a standard NestJS peer/implicit dep; referenced in config files as expected.	ai	2026/04/29
phantom-deps	phantom-dep:helmet	AI (phantom-deps): helmet is a common Express middleware configured at app bootstrap, not directly imported in library code.	ai	2026/04/29
phantom-deps	phantom-dep:class-transformer	AI (phantom-deps): class-transformer is used implicitly via NestJS serialization config; stable pattern for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@nestjs/platform-express	AI (phantom-deps): NestJS platform adapter referenced in bootstrap config, not directly imported; standard pattern.	ai	2026/04/29
phantom-deps	phantom-dep:@zthun/helpful-reflection	AI (phantom-deps): Same-org dep used implicitly via reflection decorators; stable false positive for this package.	ai	2026/04/29

Versions (showing 32 of 32)

Version	Deps	Published
1.20.0	23 / 12	2026-04-26
1.19.0	23 / 12	2026-02-14
1.18.5	23 / 12	2026-02-01
1.18.4	23 / 12	2026-01-31
1.18.3	23 / 12	2026-01-04
1.18.2	23 / 11	2025-11-07
1.18.1	23 / 11	2025-10-30
1.18.0	23 / 11	2025-10-29
1.17.0	23 / 11	2025-10-29
1.16.0	23 / 11	2025-10-28
1.15.0	23 / 11	2025-10-27
1.14.1	23 / 11	2025-10-26
1.14.0	23 / 11	2025-10-25
1.13.0	23 / 11	2025-10-25
1.12.0	23 / 11	2025-10-25
1.11.0	23 / 11	2025-10-25
1.10.0	23 / 11	2025-10-23
1.9.0	23 / 11	2025-10-22
1.8.0	23 / 11	2025-10-22
1.7.1	23 / 11	2025-10-21
1.7.0	23 / 11	2025-10-21
1.6.0	23 / 11	2025-10-20
1.5.0	23 / 11	2025-10-14
1.4.0	23 / 11	2025-10-12
1.3.5	23 / 11	2025-10-04
1.3.4	23 / 11	2025-09-09
1.3.3	23 / 11	2025-09-06
1.3.2	23 / 11	2025-07-18
1.3.1	23 / 11	2025-07-01
1.3.0	23 / 11	2025-06-29
1.2.0	20 / 9	2025-06-22
1.1.0	20 / 9	2025-06-21

v1.20.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.

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.18.5

1 finding

LOW No provenance attestation provenance

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

v1.18.4

1 finding

LOW No provenance attestation provenance

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

v1.18.3

1 finding

LOW No provenance attestation provenance

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

v1.18.2

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.

v1.18.1

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.

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.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.

v1.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.

v1.1.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.